yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
Does this not mean that the downloaded file is damaged/corrupted?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] deepankarverma:
thanks to developer, project is great

but it worked partially for me in hydrogen 32 gb, also it leads to bigger problem like booting issue, even after flashing twp, it took me a day to get my device running healthy, even fastboot flashing through bootloader did not worked, after doing fresh clean install by "edl mode" i got my device running.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Sense7606:
Something is definitely wrong here. I can't flash anything with this Recovery. Tried flashing an incremental update and ended up with a "Zip file is corrupt" error. Activated "Support MIUI incremental OTA" and "include system in OTA survival", tried to flash current full Rom and still got the "Zip file is corrupt" error. Then I tried to flash the updated full Rom(latest) and I still got the same error. Either there is something wrong with all MIUI Roms or this Recovery, or maybe there is something I'm doing wrong.

Lastly I tried flashing magisk and I got a "Lucky Patcher" error and I don't even have Lucky Patcher installed. It seems there is something definitely wrong with this Recovery.

MI Max 32GB

MIUI 9 Global Dev/Beta 8.2.8.

*seems I cannot upload screenshots on this forum. ?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] raymondsanusi:
Hm..its working fine for ne...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] yshalsager:
Recovery is tested and working well, please follow the instructions here

https://xdaforums.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337

If you have lucky patcher folder on internal delete it
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Aryan Lathar:
I tried flashing new rom did what it asked but my phone went into bootloop
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
I do not think that this bootloop RedWolf related bootloop....
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] astherion:
Thanks, no need! I've tried Red Wolf on my son's RMN4, and it says that "stops works before you uninstall piracy tool Lucky Patcher"!!!:eek: Recovery that getting all info about installed apps. TWRP from nijel8 is the best, no need this junk!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
There is no need for insult.

It's not Junk. You are using applications that this is not compatible with. But taking this into consideration is not Junk. If you need Nijel's use that.

小米Max全网通版3GB/64GB银色MIUI9全球开发者8.2.8
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] yshalsager:
I won't reply to that.

I'm not here to make problems!

Can you read this?!

https://xdaforums.com/showpost.php?p=75842764&postcount=32
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] bdogan1912:
Lucky patcher - as stated- is somehow pirating software mainly used by pirating apps and cloning licences or modifiying IAP protocols. Unless you using it for a 'nice' stuff nearly every app will ask you to uninstall it to work properly because it modifies app/game files in unsupported way and its kinda illegal. If you want to install something that requires lucky patcher be removed either remove pirating software or don't even talk trash in here. People working their arse off of to make things work. You do not have any rights to complain if you have pirating/hacking app or game inside your phone.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] nijel8:
Just my 2 cents which I should probably not throw ot, at least not in this thread but... anyway...

The point of any recovery is to be completely independent of any ROM, Android, OS whatever is on that system partition... That's why it is called RECOVERY and not second system or whatever... What's the point of it if you cannot recover your system b/c something is on that system!? What if you have problems with Lucky Patcher and the only way to get rid of it/recover your system is flashing new rom. But you can't b/c of that same LP you are trying to get rid of...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] yshalsager:
I understand your point of view, also can agree with you!

But I won't make a separate fork from that project to remove anti-piracy functions! All I can do is reporting your comments to original project developers.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] dadi11:
Ok. Goodbye [emoji112]
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] astherion:
[MENTION=5501088]bdogan1912[/MENTION], Get loss about pirating apps! You are on XDA: web-sight that dedicated to modded/pirated/unofficial apps! And recovery that just get all info about my phone - not mine way. And its not your business how I'm using mine phone, so get off! And not developers business to get & collect all info about mine mobile in recovery!!!
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ZainBilq:
+1
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] bdogan1912:
Very well then get off from this thread. Don't like? Fine no one forces you to install but you cannot force the developer to remove anti pirating tool detection. Your phone? Your decision. His project? His decision. Case closed.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] crazyg4merz:
Web-sight? Is that even a word? XDA is dedicated to pirated apps? You're on the wrong place dude. There's no such rule in XDA that says pirating app is allowed.

I don't agree with the way this recovery scanning the phone and that's why I don't use this recovery. But I respect the developer's decision. This is his project, this is his thread, this is his work. And he clearly stated in the OP how he hates pirate cheap worthless **** like you (yes I hate pirates to) and he doesn't want worthless human beings like you to use his recovery. I can understand his decision, but I don't agree with how it's being done, so I don't use his recovery. It's just that simple.

Nobody is forcing you to use this recovery, nobody is asking your money to be able to use this recovery. You don't like it? Don't use it. You don't have any other choice other than this recovery? Then just fork his source code and delete the line of codes you don't like, then compile it yourself. You don't know how to do it? Then ask somebody to do it for you. Nobody want to do it for you? Pay someone to do it for you (but you're so cheap that you can't even legally acquire paid apps so I don't think you'll do it LOL).

You can voice your opinion whether you like it or not, but asking the developer to get loss in his own thread is plainly the stupiest thing to do. And I'm laughing so loud at you right now because your stupidity is too fvcking funny.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ZainBilq:
I am laughing at you why you had to write such a big reply for that guy....
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] SolankiDS064:
I Am Mi Max 32 GB 3 GB RAM User I Am On MIUIPRO 8.4.26 beta I Want To Install Global Stable

miui_MIMAXGlobal_V9.5.2.0.NBCMIFA_66a18ac56c_7.0.zip But This Zip File Not Working On TWRP Recovery I Can Install Official OTA Update On My Hydrogen Device Using TWRP Recovery

Can I install successfully this Official Global Stable zip Using Red Wolf Recovery ?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
What is your problem?

You can install global rom with nijel8's recovery and redwolf too.

Because you need:

-full clean install

-lazyflasher or any method of correcting boot
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] HannibalLecter:
you know a few months back, I never needed lazy flasher after instlaling MIUI from nijel's recovery.

But from the recent past, I run into bootloop after flashing MIUI. and need lazy flasher to make it right.

Anybody knows why is that?

also, could you link a working lazyflasher zip for max?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
As I wroted, I've used "any method"...

Install stock miui rom, after install SU and lastly CleanSU and after then miui can booting.

"...bootloop after flashing MIUI...Anybody knows why is that?..."

I think because Xiaomi has built a new defense / security tool...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Aryan Lathar:
Does the quick charge option in settings work??? Plz reply TY
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JeffyRiffic:
I can just flash this img using Twrp that is installed on my device?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] JulianJenner:
img of Redwolf? Yes, you can.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] josephkarthic:
Can I install this for MI MAX Prime (128gb) without bootloop?

Hi,

I previously installed official TWRP 3.0.2.0 for helium version and I got bootloop when I swipe allowed modifications..Im not sure why.....Can I install this and do the same to install supersu?

Will i get any bootloop? Please help?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] paarkhi:
Yes, you can install without any bootloops.... I've installed it on my helium 4gb / 128gb
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] josephkarthic:
Ok thanks, so after i enter twrp should i swipe allow modifications and flash supersu or keep read only?

Bcoz in some thread i read that it uses dm varity check and that's the reason for boot loop... It also asked for decrypt key once entering twrp.. Do we get the same in this twrp?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] paarkhi:
Swipe to allow modification and don't install superSU, better to root with Magisk, I think it has inbuilt magisk.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] josephkarthic:
Yes the features list says it has magisk, supersu and aroma...so that means i can just flash this twrp and it will be automatically rooted? Bit confused...
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] lostreal:
Hi, is this recovery still supported or an abandoned project?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] yshalsager:
Depends on Is it still useful for mi max 1 community? :confused:
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] lostreal:
Of course, I'll be looking forward the improvements. I'm sure there are others who think the same thing about it. I still love my Mi Max Prime. And thanks for the reply.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] jjrojo:
I'm using redwolf, thank you.

Edit: Hydrogen version.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] SolankiDS064:
Which Recovery Can I Install in 3GB-RAM/32GB-ROM ?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] lostreal:
Is shutdown alarm (powered off) feature working with your device? Schedule Power On/Off working perfectly even if the device connected to the charger but shutdown alarm not working with my device, I have Helium. [MENTION=6084385]yshalsager[/MENTION] can you help us about this?

You can use this recovery... [url]https://xdaforums.com/mi-max/development/recovery-red-wolf-recovery-project-t3750171[/URL]
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] SolankiDS064:
I have A one Question

RedWolf Recovery for mi max support Treble project ?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] SolankiDS064:
Please Add Treble Support (Treble Project) in Next Build 3.2_27
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] AlexandraV:
Nice works
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] migside:
Hi I found a new version from redwolf recoveryfor Helium Whats about that it's your work?

RedWolf-Unofficial-027-hydrolium? Because I don't find AFH on your profile to Download :) can I use in Android P Roms?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] ReyT_:
This is the solution

http://en.miui.com/thread-4765843-1-1.html

very simple and subtle
[Galaxy Note 4 Q&A, Help & Troubleshooting] Tcalp:
Hi Guys,

I have a T-Mobile N910T and am looking to enable native bluetooth tethering (this seems to be something that T-Mobile disables in their releases?). I tried flashing to a custom rom this morning but ended up in a reboot loop even after several attempts. I then used the ODIN tool to take me back to a stock N910TUVU2EQI2, which at least has gotten my phone running again.

Anyhow, would be really nice to have BT tether as I am looking to put a tablet in my car and would like it to pick-up my phones data connection when I"m in the car.

I feel like custom roms seem to have a bit of a learning curve to get working properly, though, I have learned a reasonable bit as I spent most of the night figuring out how to flash my phone in the first place and then recovering it to a stock rom etc. ...

Any suggestions as to what rom I should attempt to flash that would likely lead to the least number of issues, but allow me to have BT tether ?
[LG G6 Questions and Answers] SheepSaysBaah:
Hey, so I have managed to get stuck into a bootloop when installing xposed framework (I think that's what caused it, at least.)

and I have no idea how to get out of it, could somebody help, I'm a little skeptical if I'm bricked, but as far as I know I am bootlooped as the LG logo repeats itself.
[LG G6 Questions and Answers] Killua96:
If you have the TWRP installed just boot in TWRP and flash the uninstaller, and after that a stock rom.

Otherwise you can install the TWRP by booting into fastboot mode (keep pressed vol- and connect the phone to the PC), or flash the original firmware trough LGUP+Uppercut by booting in download mode (keep pressed vol+ and connect the phone to the PC)
[LG G6 Questions and Answers] mprovi_15:
This bootloop is common in the LG G6, wait 10-15 min (like 3 or 4 reboots) and you will see that the phone boots properly.

There is no information to explain why this happens, but after the first boot the following boots will be normal.

When uninstalling through uninstaller zip happens the same.
[LG G6 Questions and Answers] pizza_pablo:
This was my experience. After rooting and the first shutdown, I went to power on and bootloop occurred. While searching for answers, I found this thread and while reading this, the G6 was bootlooping between the bootloader unlocked warning and LG splash screen. While here, it had looped about 8 times and it finally just booted up.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Hardware Requirements

https://source.android.com/setup/build/requirements#hardware-requirements

Setting up a Windows Subsystem for Linux build environment

https://docs.microsoft.com/en-us/windows/wsl/install

https://source.android.com/setup/build/downloading & https://source.android.com/setup/build/building | https://wiki.lineageos.org/build_guides.html
[Android Software/Hacking General [Developers Only]] Uldiniad:
Useful resources

Run Linux GUI apps with WSL

Learn how WSL support running Linux GUI apps.

docs.microsoft.com

Get started mounting a Linux disk in WSL 2

Learn how to set up a disk mount in WSL 2 and how to access it.

docs.microsoft.com

How to manage WSL disk space

Learn how to check the amount of disk space available, expand the size of the Virtual Hard Disk (VHD), repair a VHD mounting or read-only error, and locate the .vhdx file and disk path for Linux distributions installed with WSL 2.

docs.microsoft.com

https://github.com/MicrosoftDocs/WSL/issues/412#issuecomment-575923176
[Android Software/Hacking General [Developers Only]] 1a2a3a4aq:
Hello, Thanks for your great guide. I was able to finish the build nearly successfully.

USE_HOST_BISON is opt-in, so you don't need to set it false unless you've exported USE_HOST_BISON=true before.

I've seen the change 196115, but is this change really needed for WSL build?

It seems like change for non-WSL build. (whose don't need to use prebuilt FLEX)
[Android Software/Hacking General [Developers Only]] Uldiniad:
Thanks for your feedback.

As you pointed out, I made a mistake in the number of the commit to be cherrypicked. I've corrected the OP, so, the command should now work and you can also see the code that is added by the commit by following the link. Thanks for pointing that out.

WSL only supports 64-bit binaries. That is why I've left out bison and flex from the packages to be installed for the build environment and instead have put the code to my forked repos which have prebuilt 64-bit bison and flex. Then I've set USE_HOST_BISON and USE_HOST_FLEX to false in bashrc so that it doesn't go looking for the packages that would typically be installed with apt-get and makes sure the 64-bit prebuilts are used (but as you said, it might be an unnecessary precaution but it doesn't hurt to have it).

Hope that helps. And if you have more questions, ask away.
[Android Software/Hacking General [Developers Only]] 1a2a3a4aq:
btw, using "/bin/bash -c" instead of brunch does not make effect for me.

build stucks while doing dex2oat jobs just like using brunch.

build with WITH_DEXPREOPT=false was successful, but 8.1 must use dexpreopt due to sepolicy changes. still searching on this.
[Android Software/Hacking General [Developers Only]] Uldiniad:
Ok, thanks for mentioning this. I had success with the /bin/bash -c command but if this is not universal, then, as you said, we should find another universal workaround or fix and I'll replace mine with it in the OP. I'll look into WITH_DEXPREOPT and other possibilities on my end too.

I've reopened the issue on GitHub while there is no universal fix or workaround: https://github.com/Microsoft/WSL/issues/2948
[Android Software/Hacking General [Developers Only]] Uldiniad:
I've opened this page: https://source.android.com/devices/tech/dalvik/configure

I'm thinking of trying out different makefile options instead of disabling dex2oat altogether and see if it makes a difference for the brunch command. Maybe you can do the same and keep us posted
[Android Software/Hacking General [Developers Only]] Uldiniad:
Deleted
[Android Software/Hacking General [Developers Only]] akashk07:
Thanks for posting the tutorial
[MENTION=7350242]Uldiniad[/MENTION]

I'm very thankful to you for this.

One question, is it possible to download the whole source somewhere else so that we don't have to download the complete source across windows formats and system restores?
[Android Software/Hacking General [Developers Only]] Uldiniad:
As far as I know, at this point in time it is not (that's why I put up the requirements and warnings on the OP). WSL is made to work mostly within its own environment (somewhat separate from Windows) and intercompatibility/interoperability with the Windows file system is limited. Linux and Windows don't have the same file management systems (which is why manipulating files of the subsystem from Windows Explorer and the mount option are out the window for now). Also, there is no simple way of changing the installation location of lxss as of today (although, you can check WSL's GitHub if you're really determined to move it ;)).

WSL is picky and that is why threads like this exist. If WSL worked like Ubuntu out of the box this thread wouldn't be necessary (LineageOS' guide would suffice).
[Android Software/Hacking General [Developers Only]] 1a2a3a4aq:
Check LxRunOffline on GitHub. It can install WSL distribution to another directory from tar file.
[Android Software/Hacking General [Developers Only]] :
So can this build a ROM completely?
[Android Software/Hacking General [Developers Only]] Uldiniad:
Yep. I'm currently running a build on my s5 that I made myself on the Ubuntu app for Windows 10. We are currently working on fixing the dex2oat issues but other users have suggested workarounds in the mean time.
[Android Software/Hacking General [Developers Only]] :
ok thanks bro. New to rom building, but I did build a DU rom that works for sailfish
[Android Software/Hacking General [Developers Only]] taxueliuyun:
Hello Uldiniad, thanks your guide. I got a error, When I start the build "brunch gemini":

[1055/1074] including ./vendor/qcom/opensource/cryptfs_hw/Android.mk ...

build/core/binary.mk:40: warning: libcryptfs_hw uses deprecated kernel header dependency path.

[1056/1074] including ./vendor/qcom/opensource/dataservices/Android.mk ...

build/core/binary.mk:40: warning: librmnetctl uses deprecated kernel header dependency path.

build/core/binary.mk:40: warning: sockev uses deprecated kernel header dependency path.

[1074/1074] including ./vendor/xiaomi/scorpio/Android.mk ...

waitpid failed: No child processes

19:40:52 ckati failed with: exit status 1

I have no idea, please help me, thanks. ( I run windows 10 in virtualbox)
[Android Software/Hacking General [Developers Only]] Uldiniad:
would you mind running

breakfast gemini && make bacon showcommands

just based off the snippet you gave above I can't say much about the failure, the "no child processes" failure could be because it is not finding the next tasks (possibly missing some makefiles) to be executed for some reason (which would be strange).

also, are you successfully building on other platforms? and did you follow the OP step-by-step?

note: it shouldn't matter, but I recommend running windows natively if you want to build on lxss. but on vm it shouldn't matter (that I know of). although if you're running windows in a virtual machine, what are you running natively? probably a unix-based system right? because if so, darwin or linux will have more chances of successful builds than wsl guaranteed
[Android Software/Hacking General [Developers Only]] Jain2vicky@gmail.com:
hello Uldiniad getting error while building for my kenzo

11. mini_emulator_arm64-userdebug

12. m_e_arm-userdebug

13. mini_emulator_x86_64-userdebug

14. mini_emulator_x86-userdebug

15. uml-userdebug

16. aosp_kenzo-userdebug

17. aosp_kenzo-user

18. aosp_kenzo-eng

19. lineage_angler-userdebug

20. lineage_bullhead-userdebug

21. lineage_capricorn-userdebug

22. lineage_cheeseburger-userdebug

23. lineage_dumpling-userdebug

24. lineage_gemini-userdebug

25. lineage_gts210vewifi-userdebug

26. lineage_gts28vewifi-userdebug

27. lineage_natrium-userdebug

28. lineage_oneplus3-userdebug

29. lineage_zl1-userdebug

Which would you like? [aosp_arm-eng] 16

build/core/product_config.mk:237: *** Can not locate config makefile for product "aosp_kenzo". Stop.

Device kenzo not found. Attempting to retrieve device repository from LineageOS Github (githubcom/LineageOS

).

Found repository: android_device_xiaomi_kenzo

Default revision: lineage-15.1

Checking branch info

Default revision lineage-15.1 not found in android_device_xiaomi_kenzo. Bailing.

Branches found:

cm-13.0

cm-14.

cm-14.1

lineage-15.0

stable/cm-13.0-ZNH5Y

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

build/core/product_config.mk:237: *** Can not locate config makefile for product "aosp_kenzo". Stop.

build/core/product_config.mk:237: *** Can not locate config makefile for product "aosp_kenzo". Stop.

** Don't have a product spec for: 'aosp_kenzo'

** Do you have the right repo manifest?

jain2vicky@instance-2:~/los151$
[Android Software/Hacking General [Developers Only]] Uldiniad:
Your device does not have lineage-15.1 yet. check the branches here: https://github.com/LineageOS/android_device_xiaomi_kenzo
[Android Software/Hacking General [Developers Only]] Uldiniad:
the pruning is not an error. it is saying that the project is shared (used by other devices potentially) and therefore it does not apply pruning to the tree.

the reason I wanted you to post the showcommands is so that I can see what is the last few commands before the error
[Android Software/Hacking General [Developers Only]] Uldiniad:
Lol.

you can just start repo sync again as soon as you're back on bash and keep going from there
[Android Software/Hacking General [Developers Only]] TheIronMaiden:
It had a fatal error trying to fetch the source. Also, tried to clone the h910 proprietary source, and it had an upstream error. Didn't copy the error code, forgive me

Sent from mTalk
[Android Software/Hacking General [Developers Only]] Uldiniad:
without logs I can't really help