Related
just finished rooting and flashing twpr recovery 2.6.3.0
every thing is okay
but when trying to flash twpr 2.7 it sayes
target reported max download size of 1542111232 bytes
error: cannot load 'openrecovery-twrp-2.7.0.0-t6ul': No error
what is this problem?
how to flash the new twpr recovery?
rowihel2012 said:
just finished rooting and flashing twpr recovery 2.6.3.0
every thing is okay
but when trying to flash twpr 2.7 it sayes
target reported max download size of 1542111232 bytes
error: cannot load 'openrecovery-twrp-2.7.0.0-t6ul': No error
what is this problem?
how to flash the new twpr recovery?
Click to expand...
Click to collapse
How are you flashing it? like, exact commands?
fastboot flash recovery openrecovery-twrp-2.7.0.0-t6ul
itried flashing the old one too but the same
rowihel2012 said:
fastboot flash recovery openrecovery-twrp-2.7.0.0-t6ul
itried flashing the old one too but the same
Click to expand...
Click to collapse
fastboot flash recovery openrecovery-twrp-2.7.0.0-t6ul.img
Looks like you forgot to add .img to the filename
thank you my friend i forgot to type img
thank you very much Vinchenzop
is their any mod to Make speaker louder ?
rowihel2012 said:
thank you my friend i forgot to type img
thank you very much Vinchenzop
is their any mod to Make speaker louder ?
Click to expand...
Click to collapse
No problem, glad that was the only issue. I'm sure there are various mods that are currently not made for the One Max that could increase speaker volume, however, those type of mods also come with the risk of damaging your actual hardware. I know it's a good bit of change, but I personally bought a JBL charge for about $150 and the sound quality is clear and loud enough to use as a primary output for house parties. That may be a better route if you'd like to avoid hardware damage to your device.
Hi, im trying to root my Huawei Y6 ii, and after unlocking bootloader, when i try to flash TWRP, i get this message
target reported max download size of 471859200 bytes
error: cannot load 'recovery.img': No error
Does anyone have solution for this please? Thank you
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
AWFRONT said:
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
Click to expand...
Click to collapse
I was going to do the same but I got tired of the ads and bloatware, so I needed root to install AdAway and Titanium Backup to clean the preinstalled programs
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
doctahjeph said:
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
Click to expand...
Click to collapse
That is what they recommend on the other site. I do not know why.
once you've done this, does it block OTA updates from Asus?
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
I think so.
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
Once you unlock the bootloader the OTAs are blocked, even if you aren't rooted. It is okay you can still manually install the firmware easily.
mushufasas said:
[
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Click to expand...
Click to collapse
I updated it & still have root
I have rooted again on latest firmware and used Supersu 2.79. Works as advertised so far.
Gone Looking
mushufasas said:
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Click to expand...
Click to collapse
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
av8or091 said:
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
Click to expand...
Click to collapse
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
av8or091 said:
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
Click to expand...
Click to collapse
I do not know why, but I had to reinstall the rom on my phone, used the same files for root and it worked with no problem.
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Suggested Edit
mushufasas said:
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Click to expand...
Click to collapse
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
signature verification failed
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
krcma.cz said:
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
Click to expand...
Click to collapse
i flash downgrade fw WW-14.1010.1703.42
and flashing of supersu still not working
any idea ?
av8or091 said:
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
Click to expand...
Click to collapse
seems like all went well for me . . . unlocked / twrp / superuser / even the upgraded kernel & software upgrade ........ but the system hangs on the start screen ... but upon restart - the zenphon still goes into bootloader & twrp if i want to.
I don't suppose anyone made a twrp backup of a fresh / no added programs? Even one w/ bloat removed?
anybody able to show a bit of love?
thx in advance
Bummer . . . . no one's made a twrp backup yet? That's one of the 1st things i do - just in case.
.
Is it possible to update to new version of SuperSU then 2.80 ?
I try to update SuperSU with TWRP to version 2.82-201705271822.zip but installation failed....
Important notice: This is an outdated modded recovery which only works with nougat. Use the newest one instead. It supports both Oreo and Nougat rom porting.
Modded TWRP 3.1.1-0 Download:
Google Drive
How to install:
- Unlock bootloader
- Enter in Fastboot Mode (Power Button + Vol Down)
- Flash using "fastboot flash recovery twrp.img"
Mod features:
- Automatic A1 Rom Porting
- Included Magisk 14.5 installer
- Included AROMA Filemanager
Where can I find the new features?
Go to Advanced menu and then tap on "Aex12 Toolbox". A new menu will open with the new 3 options (Port A1 Rom, Install Magisk, Aroma FM)
How does A1 automatic ROM porting works?
Install any Nougat A1 ROM directly on your 5X, but make sure you only install system.img and boot.img, if you flash other partitions you will probably face some errors. Then tap on "Port A1 Rom" button. Confirm that you want to make the port using the slider. Wait until it finishes. Reboot and enjoy.
How can I flash an A1 rom into the 5X?
If you downloaded an official rom, extract it somewhere, enter the directory and look for the "images" directory. Enter on it, open terminal on this directory and then execute this commands:
fastboot flash system system.img
fastboot flash boot boot.img
After it finishes, go to TWRP and use the "Port A1 Rom" button
Fingerprint is acting as a button after porting A1 rom
You need to flash A1 firmware to avoid some minor bugs like this.
Will it work with Oreo?
It does not work with Oreo at the moment. I'm working to make it work. As soon as I got it, I will add an automatic Oreo porting button.
Does this works with custom ROMs?
I didn't try, try it yourself and comment results
Where is the changelog?
You can check it here
Donations:
If you like my work and want to contribute, you can donate via paypal.me/aex12
Device Tree: https://github.com/Aex12/android_device_xiaomi_tiffany/tree/nougat
Manifest used: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
XDA:DevDB Information
TWRP Modded 3.1.1, Device Specific App for the Xiaomi Mi 5X
Contributors
Aex12
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.1.1-0
Created 2017-12-05
Last Updated 2018-03-08
Good job. Thank you.
Thank you.
Thank you :good::good:
hello thank you, but I have 1 problem, I can not access the micro sd card, by twrp.
Best Regards
Please help to mirror modded versions to mega Drive too, Thank you.
Google is blocked in my country. Even if I use some proxy tools, it still hard to download anything from Google drive.
I have tried everything I can...
I followed the exact procedure word to word on my Mi 5X (It has Nov update before)
downloaded an official rom, extract it somewhere, enter the directory and look for the "images" directory. Enter on it, open terminal on this directory and then execute this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
After reboot to system the error showed telling "No Command" with no system to boot. Fortunately I had Nov Update so installed it in TWRP and got back to system. Detailed instructions will be appreciated.
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
AncientLord said:
I followed the exact procedure word to word on my Mi 5X (It has Nov update before)
After reboot to system the error showed telling "No Command" with no system to boot. Fortunately I had Nov Update so installed it in TWRP and got back to system. Detailed instructions will be appreciated.
Click to expand...
Click to collapse
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Aex12 said:
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Click to expand...
Click to collapse
Thanks for the tip. I missed that step. I followed the steps to the letter now and flashed system.img and boot.img from December ROM as indicated by the attached photo. But the mobile is still on November Patch level. Done that twice to no effect.
AncientLord said:
Thanks for the tip. I missed that step. I followed the steps to the letter now and flashed system.img and boot.img from December ROM as indicated by the attached photo. But the mobile is still on November Patch level. Done that twice to no effect.
Click to expand...
Click to collapse
Phone is updated, but version displayed on settings is wrong. It's an known bug. Flash fixed recovery and tap on "A1 Rom Porting" again. You don't need to flash system.img and boot.img again.
Aex12 said:
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Click to expand...
Click to collapse
Aex12 said:
Phone is updated, but version displayed on settings is wrong. It's an known bug. Flash fixed recovery and tap on "A1 Rom Porting" again. You don't need to flash system.img and boot.img again.
Click to expand...
Click to collapse
This time it worked. Thanks you for your great effort. Much appreciated.:good:
Can you give me a brush adb file?
I tried to flash the December update system.img and got an error about not enough space. Like the image was too big to flash.
i flash system.img and boot.img but i cannot ota update
Sent from my Mi A1 using XDA Free mobile app
zzzwww said:
Can you give me a brush adb file?
Click to expand...
Click to collapse
You can find it here:
https://developer.android.com/studio/releases/platform-tools.html
---------- Post added at 02:11 PM ---------- Previous post was at 01:23 PM ----------
wailinhtike said:
i flash system.img and boot.img but i cannot ota update
Sent from my Mi A1 using XDA Free mobile app
Click to expand...
Click to collapse
No, you can not update 5x with mi a1 rom via ota.
Getting this when trying to flash system. How do I fix this?
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.219s]
sending sparse 'system' (522959 KB)...
OKAY [ 19.155s]
writing 'system'...
OKAY [ 2.803s]
sending sparse 'system' (502018 KB)...
OKAY [ 18.197s]
writing 'system'...
OKAY [ 2.504s]
sending sparse 'system' (524297 KB)...
FAILED (remote: data too large)
finished. total time: 47.065s
gurex said:
Getting this when trying to flash system. How do I fix this?
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.219s]
sending sparse 'system' (522959 KB)...
OKAY [ 19.155s]
writing 'system'...
OKAY [ 2.803s]
sending sparse 'system' (502018 KB)...
OKAY [ 18.197s]
writing 'system'...
OKAY [ 2.504s]
sending sparse 'system' (524297 KB)...
FAILED (remote: data too large)
finished. total time: 47.065s
Click to expand...
Click to collapse
Are you on a Mi 5X and installing Mi A1 rom? It should flash well as both phones have same system partition size. For me it worked.
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Aex12 said:
Are you on a Mi 5X and installing Mi A1 rom? It should flash well as both phones have same system partition size. For me it worked.
Click to expand...
Click to collapse
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
gurex said:
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
Click to expand...
Click to collapse
Max download size is not the problem. Mine is also the same. Fastboot will just divide system.img in chunks of 500mb approximately each of. Try downloading newer fastboot binary.
https://developer.android.com/studio/releases/platform-tools.html
Aex12 said:
Max download size is not the problem. Mine is also the same. Fastboot will just divide system.img in chunks of 500mb approximately each of. Try downloading newer fastboot binary.
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Will try it when I come home today and report back!
Hi,
i tried to update to OpenKirin RR Beta 3, but flashing failed with fastboot (fastboot flash system C:\Daten\rr3.img.xz)
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (460796 KB)...
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
OKAY [ 10.747s]
writing 'system' 1/2...
FAILED (remote: sparse flash write failure)
finished. total time: 14.841s
Click to expand...
Click to collapse
I had installed magisk with OpenKirin beta2 before. After failed flashing the device tries booting a few times but then it boots to eRevovery.
I tried flashing -kernel-recovery-ramdisk 368 from @JBolho Thread (https://forum.xda-developers.com/honor-9/how-to/emui8-kernel-recovery-ramdisk-stock-t3781347), because i thought something went wrong with the patched boot.img from magisk. But no success. Still bootloops and ended in eRecovery.
Can somebody help?
Thank you
P.S.: I posted this question in https://forum.xda-developers.com/honor-9/development/roms-openkirin-aosp-collection-t3828787/page3 too, but i don't know if somebody reads it there.
You tried to flash the compressed file instead of extracting the img file from it...
JBolho said:
You tried to flash the compressed file instead of extracting the img file from it...
Click to expand...
Click to collapse
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Saftpresse99 said:
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Click to expand...
Click to collapse
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
JBolho said:
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
Click to expand...
Click to collapse
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Saftpresse99 said:
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Click to expand...
Click to collapse
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
JBolho said:
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
Click to expand...
Click to collapse
What can i do to determine the correct version?
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Saftpresse99 said:
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Click to expand...
Click to collapse
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
JBolho said:
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
Click to expand...
Click to collapse
Thanks. Installed twrp, but can't get FullOTA from firware finder: http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action Site is down. :crying:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Saftpresse99 said:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Click to expand...
Click to collapse
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
JBolho said:
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
Click to expand...
Click to collapse
Hi,
thank you very much. My device is now working again. Your instructions working very well. I flashed stf-L09c432 B360 with HuRUpdater and device boots. I donwloaded the firware from this site: http://huawei-firmware.com/phone-list/huawei-honor-9