yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] ccook18:
Nodiced today that Resurrection Remix Pie came out for the nexus 5, wanted to try it out. When installing the Open GApps for it (9.0 pico), it is giving me error 70 "insufficient storage". I know that this is solved by resizing the system partition, but I have no clue what I am doing and cannot find much on how to specifically do it. What confuses me more is my previous rom was Unlegacy 9.0 with pico gapps and I had no issues while installing...

For now I am just going to restore my backup of Unlegacy.

Any help would be appriciated!
[Nexus 5 Q&A, Help & Troubleshooting] mandayugana:
There are alternative flashable zip file in telegram group (https://t.me/Nexus5chat). It doesn't touch userdata partition so we don't need to lose our data in userdata partition.
[Nexus 5 Q&A, Help & Troubleshooting] sudar0489:
Error 70

Try MindGapps 9.0, mine works well.
[Nexus 5 Q&A, Help & Troubleshooting] sanwenyu:
​Just because different roms have different size ,so you can change the partition size or switch roms .And if you want change partition，you can follow this , it may help you

https://xdaforums.com/google-nexus-5/orig-development/repartition-nexus-5-repartition-t3844395
[Xiaomi Mi 9 Questions & Answers] justinxfan:
I have relatives in China who want to buy me a Xiaomi Mi 9. I live in Canada and I want to flash global rom and use it like a global phone. How can I flash over to the Global rom from the chinese version and will Google pay and widevine work?
[Xiaomi Mi 9 Questions & Answers] vtec303:
Hope this helps, cheers.

https://xdaforums.com/Mi-9/help/carrier-aggregation-europe-t3926573
[General Questions and Answers] FortressNoah:
Is Mi Max 3 4/64 variant have a Chinese rom version? or the 6/128 has only with a Chinese rom version?If so Can I flash my mi max 3 4/64 variant global version to china version? TIA!
[Android General] HPM8294:
DELETED
[Android General] SacredDeviL666:
Thread Closed
[Android General] HPM8294:
​

Features:

- APPLICATION Turbo Colors: Application dedicated to screen settings such as saturation, color intensity, total RGB control, gray scale, color inversion, contrast, brightness value, etc.

Note: 100% support of kcal, kppd, compatible with Kernel Adiutor and EX Kernel

- Blocking advertising throughout the phone: No advertising in any application or on the page you are browsing, enjoy the freedom of not having publicity

Note: do not use advertising blocking applications, the MOD is pre-configured

Requirements

- TWRP

- ROOT

RECOMMENDED INSTALLATION STEPS

If you install a ROM from scratch it is recommended:

Make WIPES, System, Data, Dalvik / Art Cache, Cache

Install ROM

Install KERNEL

Install GAPPS

Install XPOSED

Install Turbo Evolution

Restart

If you do not want to delete your data

Make WIPES: Dalvik / Art Cache, Cache

Install Turbo Evolution

Restart

If it did not work do the installation from scratch

If you already have the mod installed, just install and restart

News v0.3 | 05/05/2019

- Ghost screen solution - Login and downloads to Huawei Music

- Integration applications with HTC, SONY, MOTO / LENOVO, ASUS, BLACKBERRY, SAMSUNG

- Download applications from other brands in Play Store, like the previous ones

- Compatible with all ROMS including Stock and AOSP.

- Integration from android 5.0 to android 9

- Compatible with other brands of equipment.

- Professional Mode in MOTO Camera

- Application update

- Turbo Colors screen

Download:

Android File Host

Blog: Turbo Evolution Spanish

Credits:

@savoca

@MrBIMC

Copyright © 2019 By HPM8294

XDA:DevDB Information

Turbo Evolution, Tool/Utility for all devices (see above for details)

Contributors

HPM8294, HPM8294

Source Code: https://github.com/savoca/kcal/commits/mdp3

Version Information

Status: Stable

Created 2019-05-06

Last Updated 2019-05-05
[Android General] HPM8294:
Please close this thread, apologies for the inconvenience generated
[8125, K-JAM, P4300, MDA Vario General] pavel989:
ok so, ive noticed recently that my TMO MDA, takes a while to load correctly on an incoming call, because it has to rotate the display, even tho i put it in normally.

turns out...

my case has magnets at the top, and no matter how i put the fone in, it will pick up that magnet, and rotate itself, then rotate back. WHY?????????

i was thinking that i could just like basically find the component ( if ur looking at the back, its toward the bottom left, behind the stylus holder) and remove it.

but maybe theres a better way?

any thoughts?
[8125, K-JAM, P4300, MDA Vario General] joemanb:
wouldn't it be easier to take the magnets out of the case? replace them with velcro or something? I certainly wouldn't alter my phone so it works with the case.
[8125, K-JAM, P4300, MDA Vario General] mr_deimos:
That's because the sensor is a reed switch. When the keyboard slides out, a magnet on the keyboard moves close enough to the switch in the other half of the phone to activate it.

Removing the switch (even if you found it - they can be really tiny) would result in phone screen not rotating with keyboard slided out, and you probably wouldn't want it, would you? I'd say to modify the case with velcro or some diffrent locking mechanism, or get another case instead.
[8125, K-JAM, P4300, MDA Vario General] pavel989:
that would make sense

ima try to modify my case then. thanks for the immediate response!
[Galaxy Note GT-N7000 Android Development] lee.wp14:
LineageOS 16.0

LATEST BUILD

lineage-16.0-20210211-UNOFFICIAL-n7000

kernel-e604934cd028ba34c8a52d6898658a2e6053ad8e (hikuii597)

magisk-v21.4

NOT WORKING/UNTESTED

- GPS/AGPS: untested, A-GPS not working

- DRM: untested

- IPv6: no connectivity

- Bluetooth: in-call audio not working

- WiFi: extremely reluctant to auto-connect

- Kernel: app requires restart to use storage after granting storage permission

- Kernel: random reboot freeze at offline charging

- Kernel: requires toggle MagiskHide on each reboot to enable MagiskHide

BUILD-SPECIFIC NOTES

- PowerHAL has been removed to provide flexibility in adjusting CPU governor.

INSTALLATION NOTES

- When prompted in TWRP, do not install TWRP Updater app as it will cause softbrick.

- To pass SafetyNet, you must use boot_magisk.img and toggle MagiskHide on every boot.

- Do not update Magisk! Always stick to the version that the build provides.
[Galaxy Note GT-N7000 Android Development] Zolo2000:
Hello,

We will have Android Pie on N7000 !!!!

Great and thank you !!!

I will buy a new battery for my Note I think.
[Galaxy Note GT-N7000 Android Development] D@rekills4:
Oh my god!

Got my N7000 out of the closet and charging it right now! Gonna flash this right away!

Thank you, [MENTION=6944026]lee.wp14[/MENTION]
[Galaxy Note GT-N7000 Android Development] D@rekills4:
@lee.wp14, it works! It actually works great!

I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.

I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.

But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I see, thank you for this information.

I will try repartitioning in the next build.

Right now, the ROM is working great!
[Galaxy Note GT-N7000 Android Development] 01000010:
GREAT! I am eager to try it as soon the RIL works! (still using this ancient phone as a backup)
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Release 20190522

CHANGELOG

20190522

- Removed unused LTE network option in Settings

- Fixed GPS and RIL functionality

- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)

- New cursor icon for stylus (thanks to ComicoTeam)

- Added xt_hl support in kernel

Notes:

- Be patient when the phone is booting up, if you have a sim lock, wait a while before entering the PIN because telephony stuffs might still be loading. You will get SIM unlock failed error if the telephony stuffs are not loaded finish yet. We are using a 2018/2019 Android on a 2011 phone, be patient :)

- GPS is tested OK personally by me prior to this release. If you can't get a fix or detect any satellites, make sure your GPS antenna connection is ok.

- Due to upstream changes, we are currently using Autosleep driver to let the phone enter a suspend state (doze). A shorter standby time should be expected.

- Builds are not SafetyNet OK and also not pre-rooted. If you want root, you may flash the addonsu package from LineageOS's website.

- Builds have signature spoofing enabled by default (thanks to rINanDO), you may take advantage of this to replace GAPPS with MicroG.

- This build is tested OK with GAPPS (pico ARM 9.0), please expect a longer boot time if GAPPS is installed.

- I'm not sure why, but earlier before this after I made some changes in the sources, the USB dialog won't show in Notifications panel anymore. To change USB operating mode, go to Settings > Connected Devices > USB
[Galaxy Note GT-N7000 Android Development] John Moore:
Quote:

1. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.

2. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)

Unquote

That means I need to flash TWRP twice from stock recovery?
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.

To make things clearer, here is a detailed list on instructions to prepare for it:

> If you are from stock ROM

1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5

2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip

3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip

4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
​

> If you are from Custom ROM

1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.

2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
​
[Galaxy Note GT-N7000 Android Development] John Moore:
Thanks very much, Lee.
[Galaxy Note GT-N7000 Android Development] Zin Bo:
I Can't boot to twrp 3.1.0 EMU Migtation

I can install and boot to TWRP 3.x IsoRec Recovery,

But after installing Twrp 3.1.0 EMU Migration

i can't boot up into that twrp

Stuck and reboot again in logo

Please help me
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Can you reconfirm the situation and possibly list out your procedures?
[Galaxy Note GT-N7000 Android Development] Zin Bo:
First, my n7000 is in Stock rom.

I flash Philz-cwm recovery.tar with odin and boot into recovery .

And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery

Then flash twrp 3.1.0-isorec.zip and reboot into recovery

And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)

So i start doing step-2( that you tell for n7000 pie rom installation )

I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)

So, I reboot into recovery again.

But then,loop in samsaung logo - boot again and again.

Can't go to Twrp

Thank for your reply.
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Can you flash back to stock to make sure everything is still OK and repeat the procedures again and stop before the step of flashing the twrp emu isorec.

Instead, extract the boot.img from the rom zip and copy to phone (you can do it using TWRP usb mtp) or sdcard, inside TWRP choose inage flash mode, and flash the boot.img to Boot partition.

Next restart to TWRP again. If you can go into twrp then you may try flashing the twrp emu isorec. See if it works this time.
[Galaxy Note GT-N7000 Android Development] dclou:
Dear Lee.wp

Thank you for the contribution to PIE ROM...

Could you please let us know, whether this ROM is OK to use Magisk or not?

Appreciate the reply from you in advance...^^
[Galaxy Note GT-N7000 Android Development] lee.wp14:
Galaxys2/n7000 won't support magisk as our kernel 3.0.101 does not support namespace, which is required for magisk to operate.
[Galaxy Note GT-N7000 Android Development] 01000010:
Is this ROM Treble based?
[Galaxy Note GT-N7000 Android Development] J..J:
100% working - usage now possible in a productive manner

So, Ive tested the last new release several weeks: No problems anymore. It works like a swiss clockwork.

I say: Perfect! :D

J..J
[Galaxy Note GT-N7000 Android Development] asusgarb:
Today I tried to install this rom.

I started from a stock non-partitioned ROM.

I followed this procedure:

1. Install tar.md5 TW kernel.

2. Install NightOwl kernel with twrp.

3. Update twrp isorec.

4. Flash i9100 emu kernel.

And here I stopped. When I rebooted recovery to flash repartition, the device goes in bootloop in start screen (black with with white Samsung Galaxy Note GT-N7000 and yellow triangle).

So I reflashed tar.md5 kernel and did passages again. But lo luck with ANY TWRP.

Now, even after flashing TW firmware with stock or modified pit file, if I flash bauner's kernel with isorec the device goes in start screen bootloop.

So now the only rom i can flash Is cm11.

Can I try to flash lineage 14.1 from philz or Cwm?
[Galaxy Note GT-N7000 Android Development] asusgarb:
EDIT:

I managed to install Lineage 14.1 and to boot into twrp recovery, but now under the twrp logo appears the name of the EMU recovery. Probably that was the problem. Can I completely erase any trace of emu recovery and go back to "stock" twrp? Because now, everytime I try to install some files made for n7000, I have a red line error saying "this file is for n7000 but this device is i9100"
[Galaxy Note GT-N7000 Android Development] dclou:
Could anyone knows if this ROM is ok to install Xposed framework

Seems that we need magisk to install Xpoosed framework....

but magisk isn't available in our pie ROM..

Need your help to instruct me.... very appreciate for your kindly assistance:)
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Little Confusing!

Thank you very much [MENTION=6944026]lee.wp14[/MENTION] for your work,

The instructions in OP are clear, but things got a little confusing when I reached here. My N7000 currently has bauner's Lineage 14.1 and TWRP 3.1 IsoRec, and I haven't done anything yet. I thought to read the whole thread before starting

If I want to flash this 20191009 build directly, can I flash the kernel and recovery: boot-222aec6.img and i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img using my current TWRP 3.1 IsoRec; then partition and proceed to flash the build? OR do I have to first flash TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip and partition first as per OP, and then update kernel and recovery for this build?

:confused:

EDIT 6 Dec:

Since nobody answered, I decided to experiment. I made a little modification and it worked great.

First, I partitioned using my N7000 lanchon-repit file, just modified it similar to the one here, i.e. lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip. Then flashed the latest TWRP-3.3.1 recovery and boot-222aec6 as per instructions. Rebooted to recovery and flashed 20191009 build without GApps. I wanted to compare performance with and without GApps.

After some rom testing, I tried to flash the latest open_gapps-arm-9.0-pico-20191204, but it would immediately abort with a mysterious "Digest Verification" error! After several failed wipe, re download, reset, re-flash rom and GApps together experiments, I remembered one post with GApps problem and it was in GApps itself. so I tried the earlier GApps release open_gapps-arm-9.0-pico-20191127 and it worked. It turned out the 20191204 release was faulty. it's now removed from GApps site and latest is 20191127. After reboot and Google sign in, I felt the phone became sluggish, so I did a factory reset, and it became smooth again . This is also recommended by Lineage website if you boot to the rom before installing GApps

I will continue testing for the next few days and give you some feedback, but so far I'm pleasantly surprised. I never imagined Note 1 would get Pie. Thank you so much [MENTION=6944026]lee.wp14[/MENTION] and everyone who made this possible. I understand you're busy with your studies and may not be following this thread. I just would like to wish you all the best :highfive:
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Proper Battery Meter Reset Procedure

Does anybody know what this actually does, and the proper procedure to reset the battery meter?

After editing ro.max17041.fg_reset_soc=0 to =1 in /system/build.prop, I tried several full battery charge and reboots. The battery level dropped by 10-30% after reboot. Is this normal, and when should I set it back to 0?
[Galaxy Note GT-N7000 Android Development] darkdragon-001:
The necessary patch seems to be possible to backport to older kernels:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Requirements
[Galaxy Note GT-N7000 Android Development] darkdragon-001:
I noticed a problem with the embedded contacts (com.android.contacts): When I receive a contact via Whatsapp and want to add it, it doesn't apply the "address" field (other fields like e-mail, phone, birthday are applied).
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Kernel panic

I used the latest release without problems for 3 weeks. Only once I got a kernel panic, but worked fine after restart. Today I got another kernel panic, and when I restart it goes back to Kernel panic. Also if I try to go to twrp recovery, it loads briefly and then goes to kernel panic :crying: and I can only go to download mode.

I thought the kernel got corrupted and if I re-flash kernel-222aec6 using Odin it might work. So I converted boot-222aec6.img to boot.tar and also boot.tar.md5 and tried to flash both as AP with different Odin versions, but it always failed or didn't get past SetupConnection.

Any ideas???
[Galaxy Note GT-N7000 Android Development] asusgarb:
Is there anybody who can help me? Now I have a new Realme X2 Pro so my old Note3 will become my 2ndary device, but I would like to give my Note 1 to my friend. Everything is working, but he would like to use it to make practice with root etc, but that problem would block almost every try, because now it appears as I9100.
[Galaxy Note GT-N7000 Android Development] asusgarb:
I don't know why but I did the whole procedure, with also a Odin clean install before, but the modified twrp is still there. If I flash bauner's kernel with twrp included, when I open recovery I have the i9100 modified one and I can't install anything. If I want 14.1 I have to flash it with philz recovery, but on boot I have modded recovery again.

So I cannot flash any zip, included the one to remove isorec.
[Galaxy Note GT-N7000 Android Development] Gold Mix:
Were you able to boot to cwm recovery after flashing with Odin? If you select auto reboot in Odin, phone will reboot to cwm recovery automatically. Then you can flash bauner kernel from cwm and do a factory reset before rebooting recovery. I repeated the steps a number of times without doing a factory reset and it was always going back to emulated twrp! But after I did factory reset it worked.

I think the issue you are facing is because N7000 doesn't have a separate recovery partition. I have no idea where the developers are installing the modified recovery, or if they are installing in the same location. [MENTION=6944026]lee.wp14[/MENTION] has done a great job with this rom, but unfortunately for us, it seems he's too busy studying and abandoned the project.

I don't know if my case is different than yours. I believe you have TWRP-3.1.0-EMU-MIGRATION. I didn't install this one. I started immediately with i9100-Emulated-Storage-TWRP-3.3.1-1 in post #2 which is required for the latest release 20191009. Maybe you can flash this one and try the procedure and see if it works. There is also a newer kernel for the latest release, maybe it's required for twrp to work (make sure you follow instructions in post#2 "README FIRST" ). Also, you haven't done the re-partition, maybe it's required. Who knows?

You see, without dev guidance we are just walking in darkness in a guessing game. But I'm sure if you keep on trying you will eventually find a way, and learn something in the process. I almost gave up on my phone recovering from permanent kernel panic, but after several hours of trying many different things it finally worked.

Another idea: If you have gone this far, installed emu twrp 3.3.1, kernel-222aec6 and re-partitioned, maybe you can first try latest release 20191009 and see how it works for you. I really like it, and was going to write a generally positive review about it in spite of few bugs (one of them is serious), when I was struck with a permanent kernel panic out of the blue. I fixed it 5 days ago and since then I have been using my device continuously, and everything seems fine so far. Maybe it was just bad luck or a certain incompatibility issue.
[Galaxy Note GT-N7000 Android Development] Gold Mix:
[MENTION=2718581]asusgarb[/MENTION]

If all fails, maybe you can post your question in I9100 Lineage 16 thread. [MENTION=6944026]lee.wp14[/MENTION] borrowed I9100 recovery since i9100 and N7000 have a lot in common. Hopefully, the dev there is still active or other people have some knowledge and can help you. Please keep us posted so we can all benefit

Good luck :)
[Galaxy Note GT-N7000 Android Development] jay1553:
Before I install this ROM, will the S pen still work? (Sorry for being a newbie) :o
[Galaxy Note GT-N7000 Android Development] Gold Mix:
I think it does somehow, I can see it's doing something. I don't know if I'm not using it properly, or if it's not as good as stock, but I find the pen to be very inconvenient and slow, and prefer to use finger. Besides, you won't have those Samsung apps, that are designed for s pen.

I never used stock on this phone to be able to tell. It was my sister's, and when she didn't want it anymore, she gave it to me to play with :laugh: When I saw it still has JB, the first thing I did was to head to xda and searched available roms, and chose bauner's Lineages 14.1 Nightowl. Maybe you can try it first, and see how it works for you. It'll be a lot easier for you to go back to stock if you don't like it. Besides, some of the steps of that rom are prerequisites for this rom anyway.
[Galaxy Note GT-N7000 Android Development] jay1553:
Thanks a lot! I appreciate it! *thumbs up*
[Galaxy Note GT-N7000 Android Development] umarharoon:
Can I use it on note SHV-E160L

hi, I am new to this forum. i have galaxy note SHV-E160L with custom rom of android 4.1.2. I want to confirm if this firware can be installed on galaxy note shv-e160l?

Also right now there is no option of Cast screen in it. Will i be able to use this function if i upgrade it? I want to use the note for screen casting purpose. Thanks in advance.