yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] ToRm3nTeD:
Same situation

I am also currently trying to cook a custom ROM for HTC PAND100.

I have an O2 XDA Argon and am trying to get HTC rom onto it.

although this is beyond my skill level also, the tools supplied by the likes of buzz/pof/etc (sorry for the ppl I missed) make this quite easy

Im am very close to cracking it but need a copy of an O2 rom image.

Is there an easy way to extract the ".nb" files from my device? e.g buzz' tool that dumps a ".bin" file or an easier method?

I have a copy of the HTC RUU and extracted ".nb" files if anyone requires this for comparison/wants to swap sum Panda files.

Cheers people.

ToRm3nTeD
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Welcome, I have Xiaomi Redmi Note 4X Global. I've had my new phone for a week. Right after the first boot I updated it to MIUI 9, unlocked bootloader, installed root, exposed etc.

Everything was working fine without any problems. Today I wanted to try something new and I installed Resurrection Remix OS. Before it I took a backup with TWRP (through PC, I got backup.ab)

I was using the new rom for a few hours but then I realised that I preferred MIUI and I restored previously made backup (backup.ab). And here came the problems.

The device after restore came into a bootloop. Xiaomi logo appeared for a few seconds, then a single vibration, restart and the same again. After this I flashed (with MiFlash) a stock

firmware for my device from [url]http://en.miui.com/a-234.html[/URL] (the right one for sure) "Redmi Note 4X Latest Global Stable Version Fastboot"

Flashing through PC has always helped to unbrick devices but I don't know why in this case it didn't.

I can still enter fastboot mode and recovery so I flashed TWRP, made a full wipe with it, and installed:

-Resurrection Remix OS

-LineageOS

-recovery zip versions of MIUI (many versions)

After installing each of those I get the same result, a bootloop. I spent rhe last hours of trying everything in different combinations and looking for any information.

Can anyone help me with this problem, has anyone even faced something like that?
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Well, try this method :

Download firmware.zip, Amy custom Rom, and Gapps.

Next, boot to TWRP and wipe (advanced wipe ~) wipe everything except internal storage or SD card.

Flash firmware.zip, followed by Rom and Gapps, Reboot.

Link to firmware : https://androidfilehost.com/?fid=673791459329068624 (credits to zile995)
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Thank you for your advice but after following your instructions and the result stays the same.
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Did you flash any mods after installing Rom?
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
I didn't.
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
If I recall right, I've had this

same issue

. So, do one thing download Recovery flashable Xiaomi stock miui Rom or download Xiaomi EU Rom, then as I said earlier boot to TWRP once again, wipe, advanced wipe > wipe everything > install stock miui > lazyflasher.zip >reboot. Lemme know how it goes.

LazyFlasher : https://www.androidfilehost.com/?fid=529152257862700328

Flash lazyflasher.zip if you flash any miui Roms other than Xiaomi eu Rom before reboot.
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
I did exactly as you said, wiped everything, installed stock MIUI recovery version and lazyflasher.

No errors appeared but when I wanted to reboot my phone after installation I got an information that

no OS was installed.

I swiped right anyway to reboot and here comes the bootloop again. :/

EDIT: Tried with both stable and developer versions

-miui_HMNote4XGlobal_V9.0.5.0.NCFMIEI_d6176de291_7.0.zip

-miui_HMNote4XGlobal_7.12.21_9a89725dfc_7.0.zip

EDIT:

I also get those errors (?) while mounting during installation.

It's red themed because I was currently using Red Wolf Recovery but I get the same results when I use cofface TWRP or original TWRP
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Holy crAp. Alright, I'm no expert with fastboot Rom or so, did you try flashing fastboot Rom? Give it a go... :c

BTW, there's a device team guide on mi forum about flashing Redmi Note 4/4x : http://en.miui.com/thread-482304-1-1.html
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
I already tried installing fastboot ROMs with Miflash and it always says "succes" in the end but the phone is in bootloop anyway after I turn it on :/
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Ohk. I'm outta answers now.

Hang on, did you try installing with TWRP? I see redwolf. What about Twrp? Try it once
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Thanks for trying anyway.
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
See my edit.

*Did you try flashing Rom with TWRP? I See redwolf. Give it a go with TWRP once.
[Xiaomi Redmi Note 4 Questions & Answers] DarthJabba9:
Did you just "wipe" everything, or did you "format data" also? I suggest that you format the data partition (there is a button for this under the "Wipe" menu in TWRP), and then install your ROM again.

You need to install lazyflasher only once - after installing a custom Recovery. - but -you must do this each time you change your custom Recovery (but only do it once) - otherwise, MIUI will not boot correctly. Note that you do not need lazyflasher if you are using a custom ROM (eg, AOSP, etc).
[Xiaomi Redmi Note 4 Questions & Answers] Spukey:
I had a similar issue after installing Resurrection Remix then trying to go back to MIUI.

I used MiFlash to install a stable rom but got a boot loop after reboot.

In the end I flashed a stable rom using Miflash using the 'clean all' option. Then without rebooting I installed TWRP via adb. Booted straight into TWRP and installed the no_verify .zip. Then used TWRP to restore a nandroid backup I had on an OTG USB drive. It then booted without bootlooping. So I used Miflash to reinstall the stable rom with 'clean all' option again. Rebooted ok like a brand new phone.
[Xiaomi Redmi Note 4 Questions & Answers] enrique/rz:
I join the cause

Hi, I join the cause @ Pr3z3s. I have tried everything. And I still have the same problem. the only thing that occurs to me is that someone gives us a backup, please do upload it, and we try to restore it in our mobile.:confused::confused:
[Xiaomi Redmi Note 4 Questions & Answers] chun_9876:
can you tell me what kind of unable to mount or unmount errors you encounter when flashing? my guess is that some of your partition is corrupted
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Yes, I tried maybe 4 different recoveries for my device.

I did both many times. When it comes to lazyflasher I did flash it but didn't help.

Tried that, same result :/

Those on the second screen I put in the previous page of this thread, like unmount of /firmware failed; no such volume

EDIT: I just tried restoring .ab backup through adb and an error while restoring EFS partition occurred so I flashed a stable ROM with MiFlash and took a backup of EFS partition.

Then I restored my backup again and after an error with EFS I restored it from a backup I had just taken - no errors appeared. Then I flashed lazyflasher and rebooted and still I'm in a bootloop.
[Xiaomi Redmi Note 4 Questions & Answers] chun_9876:
here you go, my /firmware and /efs nandroid backup, seems like you have some trouble with efs as well so i included it , and to clarify things, my device is redmi note 4x MIDO 3gb/32gb edition running on cardinal aosp 5.1.1 12/10 with global miui v9.0.3.0 firmware, dont restore backup if you have a different edition because i don't know what will happen to your device . https://drive.google.com/open?id=1a8-tjbrkV8vNKaWcBsClbVlvBADinXSB

EDIT : I'm not confident that this will fix your device because it seems that either your /firmware is corrupted, or somehow disappeared .. do tell your results though , dont blame me if it becomes a hard brick ><
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Thank you for sharing your backup but I get errors while restoring it.

EDIT: All partitions seem to be present when I go to "Backup" section. What is more, I got the same error with EFS when I was trying to restore my orignal backup.
[Xiaomi Redmi Note 4 Questions & Answers] chun_9876:
i removed my link because it seems that efs might contain device sensitive info like my IMEI and mac addresses, so dont restore my efs backup,it seemed to ended up spitting an error though. anyways, it seems that you are on TWRP , i backup-ed using redwolf, so that might result in the error, and yeah, dont restore my efs partition next try
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
No problem ;)

BTW I think I just repaired my phone. I still can't believe it.

If anyone ever faces something like that, here's what I did.

-flashed stable MIUI rom with Miflash (mido_global_images_V9.0.5.0.NCFMIEI_20171113.0000.00_7.0_global_b13588b4d7)

-flashed TWRP 3.1.1-0 through adb

-wiped everything in recovery and formatted data

-flashed MIUI recovery flashable ROM (miui_HMNote4XGlobal_V9.0.5.0.NCFMIEI_d6176de291_7.0.zip)

-flashed firmware zip from [MENTION=6800380]sachin n[/MENTION]

-flashed lazyflasher-no-verity-opt-encrypt.zip

-rebooted into recovery (warning about no OS installed showed up)

-rebooted system (without any warnings) and after ~7 minutes it finally booted ;)

I would like to kindly thank everyone in this thread for your support.
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Finally..
[Xiaomi Redmi Note 4 Questions & Answers] Zaffron:
Same problem

But it is not solving the problem in my case. Please help!!!
[Xiaomi Redmi Note 4 Questions & Answers] Zaffron:
Hello [MENTION=6248070]Pr3z3s[/MENTION] I am also having the same problem. My phone has become useless since 1 week. Can you please tell me what else you did other than these method you posted. I am in a very critical condition. No solution is working for me. My phone is still rebooting from the MI loading screen. Please anyone!!!

And [MENTION=6248070]Pr3z3s[/MENTION] did you got the same /firmware volume not found error while flashing the recovery flashable ROM ?
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
This method worked for me after trying maybe hundred times:

-flashing through PC (MiFlash) with many combinations - "clean all" and "clean all and lock" (then I unlocked bootloader again)

I flashed both stable and dev versions

-trying all recoveries (Red Wolf, cofface, official TWRP)

-deleting partitions in /dev/block in TWRP and flashing again

-formatting data and wiping everything

-flashing from sd and with adb sideload

-flashing rom and lazyflasher and firmware.zip in all reasonable orders

That's all that I recall at the moment. Methods mentioned above didn't work for me, only the one I wrote about in my previous post.

Still, I hope it works for you. Good luck.

EDIT: Yes, I had the same warning while flashing firmware, even when it finally worked for me.
[Xiaomi Redmi Note 4 Questions & Answers] Zaffron:
[MENTION=6248070]Pr3z3s[/MENTION] it's killing me brother. Do you have any personal contact where i can contact you. I am really in trouble. I am nearly dead tired. Flashed 100 times. I hope i can contact you through any other means.
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
I would like to help you but there's nothing else I could come up with. Everything that's coming to my mind is already described in my previous post, I'm really sorry.
[Xiaomi Redmi Note 4 Questions & Answers] Zaffron:
Hey budyy just a little help. Can you send me that firmware which you used. Till now i have tried hundred of methods and it ended up the same.
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
https://androidfilehost.com/?fid=673791459329068624

It was in the first reply of this thread btw.
[Xiaomi Redmi Note 4 Questions & Answers] Agustinmds:
Please I need a backup of partitions relationed with bootloader because the cellphone restart and restart and i'm running out of ideas
[Xiaomi Redmi Note 4 Questions & Answers] sohanaw:
its not working for me.

you flashed through fastboot or edl?

---------- Post added at 02:34 AM ---------- Previous post was at 02:20 AM ----------

not working for me, anybody have solution to this issue please share.
[Xiaomi Redmi Note 4 Questions & Answers] Pr3z3s:
Through fastboot. Are you sure that you also formatted data along with wiping all partitions in TWRP?

I fixed the issue with doing that when I encountered the problem again.
[Xiaomi Redmi Note 4 Questions & Answers] sohanaw:
i followed all those steps in that sequence.

i dont know why its working for you and not me?

please share anything else you find.
[Xiaomi Redmi Note 4 Questions & Answers] biits1993:
Hi, You can check this post :)

I have solved this problem in that way.
[Nexus 5 Themes and Apps] maybeme2:
Does anyone know where I can find this wallpaper?

It appeared when I tried a new launcher (can't remember which one) which I have since uninstalled.

I'm now on Nova launcher and can't find that wallpaper anywhere.

Anyone know where I can find the background image?
[Nexus 5 Themes and Apps] Bhupideol:
"C launcher 3D" a.k.a. "U Launcher 3D".
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] saltysalzig:
Is there a way to root and unlock the bootloader on CQA1?
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] ziggy71:
No, the exploit is in 5.1.1 LP. You need to downgrade, and unlock.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] saltysalzig:
Does the downgrade method work on every firmware on 7.1.1 up to CQI2?
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] ziggy71:
You have 6.0.1. I am running CQI2, but upgraded after unlocking. I have heard that there is a security patch that won't let you downgrade, but unable to verify that. Try to downgrade to 5.1.1, and see what happens.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] saltysalzig:
My apologies about the 7.1.1 thing. Yes, 6.0.1. I just downgraded from CQE1 an hour and a half ago. I had CQA1 before. I'm not quite sure about CQI2 however.
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] ziggy71:
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5 is what you need to downgrade to, so that you can begin the unlock process.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
I patched the kernel for 7.1.1 on Qualcomm Moto E4 Plus. This is useful to get Magisk fully working with modules and settings that can be saved.

I compiled the fix from the released kernel source: MMI-NPR26.58-25

Here are the unsigned boot.img and zImage, use whichever one suits your fancy to patch the kernel.

Download boot.img

Download zImage

Edit: I've uploaded a build for the regular Qualcomm Moto E4 here.

Installation:

You should backup your Boot in TWRP before installing, that way you can restore if something goes wrong.

If you have Magisk installed, you'll want to patch the boot.img using Magisk Manager. Just tap install, and patch boot rom image. Then copy the patched file back to your computer to flash it.

Easiest way is to flash the boot.img while in fastboot:

>fastboot flash boot /path/to/downloaded/boot.img
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] TheJAYpoop:
Did not work, phone would not boot after flash, had to restore stock kernel.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.

Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] TheJAYpoop:
That worked perfectly, awesome!
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
Merry Christmas! Enjoy the full Magisk experience, it was really bothering me when I got this phone about half a week ago.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] :
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] :
That would be great. I'll pm you a link since I can't post links yet. I've been spending all my spare time trying to get data working properly on both devices. I have no problem testing it.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.

Download:

unsigned boot.img

zImage
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] :
Thank you very much for taking the time to do this! Especially today. Just to point out how I installed the kernel, I simply flashed it as an img with TWRP, flashed the no dmverity/forceencrypt zip, then flashed Magisk V15.0 that was just released. It stayed on the n/a screen a minute then bootlooped a couple times, but it eventually booted just fine, so be patient with it. I had the latest Boost firmware installed and Magisk v14.6 at the time. Enjoy!
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] madbat99:
Thanks [MENTION=4136656]SeanStar[/MENTION] for the regular e4 boot.img. you rock bro. Works great. Tested, successful
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] jasonmerc:
[MENTION=4136656]SeanStar[/MENTION] would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://xdaforums.com/showpost.php?p=70492947&postcount=8793

You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25

Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] jasonmerc:
Well dang, I'm working on porting lineage 14.1 to this thing too. Maybe we should join forces.

And moto's source is in a zip file, I was hoping I could get one that was unzipped and in a github repo already, for easy syncing when trying to build Lineage 14.1
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] xhan145:
Thank you for your work. I agree that stock isn't too bad with root magisk and Xposed working fine. But lineage is pretty tasty! I will shoot you both a PM if I can assist in any way
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] :
[MENTION=4136656]SeanStar[/MENTION] check out these screenies everyone:
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] :
That sucks to hear, but although I do actually like stock on this device, that's why I build custom ROMs. Budget Motorola's never get updated more then a few times. Hopefully it will get added for future devices and ones that don't get abandoned at least.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] PimpMy5Ton:
Hey [MENTION=4136656]SeanStar[/MENTION] would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.

EDIT: The latest is NCQ26.69-56
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] SeanStar:
Considering there is no kernel source for NCQ26.69-56 on MotorolaMobilityLLC github, you're SOL, there's no easy way to patch it without the source. Sorry bud.

EDIT: I wouldn't try to downgrade either, I'm sure they updated the baseband. You'll probably knockout your service if you even try.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
It works fine for me on my Boost XT1766. I flashed the boot.img with twrp, then flash Magisk. It bootlooped briefly, then booted up just fine. I've done it numerous times.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] shezzy83:
Is this already included in your qualcomm Lineage rom?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
It's for stock. It's not needed for Lineage.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] PimpMy5Ton:
Be that as it may, it's not working here that's why I'm asking him if he can fix the latest kernel, I don't use magisk I use SuperSU

---------- Post added at 09:22 PM ---------- Previous post was at 09:14 PM ----------

I've never had a problem downgrading, I never used the partition updater, so I'm good :D
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
How about this
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] PimpMy5Ton:
Oh wow [MENTION=8947538]Goose03[/MENTION], you're the man :D
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
Np. All I did was ask nicely. It never hurts.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
Here they are. This has been happening a lot faster than it used to.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] CausticBURN:
This sure looks promising to the idiots who used the partition updater... So with NCQ26.69-56 I am SOL unless SeanStar finds some time to patch the new one?

[MENTION=8947538]Goose03[/MENTION] Good work asking them to release the source code. I think I like motorola a little more now.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
How does this have anything to do with flashing a partition updater?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] CausticBURN:
In post 24 [MENTION=6843835]PimpMy5Ton[/MENTION] was talking about downgrading from the newest build and that he did not use the partition updater. I looked up what it does and it seemed all it meant was updating to the newest build.

[MENTION=4136656]SeanStar[/MENTION] said not to downgrade it could knockout your service is why I said that.

Trying to understand what all this means, sorry I must be mixing something up here. :confused:
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] Goose03:
Downgrading the kernel shouldn't cause any problem. I've flashed Sean's patched kernel on the newer build. The only problem I've found is trying to use a newer system with old modem and oem. From what I've found with my Boost/Sprint variant, telephony stuff f/c's as a result of mixing them.
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] CausticBURN:
Alright I get it now thank you. I used to think I knew what I was doing with my LG Volt. This is quite the jump in software from the dark ages of kitkat. I will try not to be so illiterate in the future
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] soaringowl2145:
Is this patch also needed to use Xposed?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] chuman72486:
I have NCQS26.69-64-5, is there an updated patch for this kernel?
[Moto E4 Plus ROMs, Kernels, Recoveries, & Other De] b@dv3g3t@bl3s:
Hi, so I'm wanting to patch my kernel. I go to download the unsigned boot image and when it finishes the download ends with a .bin file extension and doesn't show up in twrp. Is the file supposed to end in a .img extension? If so should I just rename the file and end it with .img? Also what size is the file supposed to be? Mine shows up as 10.35 mb as opposed to the stock boot image size of 16 mb...

Any help or insight greatly appreciated.

Thanks