Develop Bugs

No longer able to boot my Note 2 into recovery mode

1. I started with fully working Samsung Galaxy Note 2 GT-N7100 (Rooted)
2. I'm a newbie to flashing ROM, and read numerous articles to build awareness (and have never used a forum before - so please be gentle!)
3. Installed ClockworkMod Recovery using "ROM Manager"
4. Flashed Slim6 (Slim-6.0.1.alpha.0.1-UNOFFICIAL-20160522-1030) ROM, then Gapps, then re-booted and all OK (Note2 seemed to work fine)
5. Kernel is now3.0.101-Haxynox
6. Spotted (and surprised) that Note 2 no longer rooted (and in particular, want to use Titanium Backup)
7. So, flashed CWM6-root-note2.tar using ODIN, resulting in "Pass"
8. Note2 still not Rooted, and suspect that I should have flashed SuperSu after Slim6 ROM and before Gapps
9. So, tried to reboot to ClockworkMod reccovery using "ROM Manager" but hangs. Tried using VOL+ and HOME and POWER (many times, and for different intervals) but see Samsung logo followed by some "stripes" on the screen (rather like the horizontal hold needs to be adjusted for those that are old enough to remember such things!), but it will not boot into recovery mode.
10. In addition, Odin no longer appears to see the Note2
11. Note2 will boot conventionally, but I'm extremely keen not to have to live without rooting and flashing capability
12. I've searched hard for hints for this particular issue, but would really appreciate some advice, at least so that I don't make my beautiful Note2 any worse (and hope I've not missed any posts that I should have spotted!).
13. Please let me know if I've missed any key information.
Thanks in advance.

Flash the tar version of TWRP for your phone using Odin. You can root by flashing supersu from TWRP.
CWM is very outdated and cannot be used to flash current custom ROMSs.

Many thanks, I've moved over to TWRP and it seems much better.
I also tried to find a more "suitable" (reliable) ROM and chose Resolution Remix, especially as services kept stopping on Slim6.
So now I can get to recovery mode, but still I have issues. Mainly...
a) I've so far failed to flash a compatible Gapps file
b) I've flashed supersu and busybox (Root_SuperSU.0.98-Busybox.1.20.2-signed.zip) but root is still not available. Sometimes I see a "Grant" prompt but it hangs for ages when I grant. The SuperSU app can be seen, but is not responsive. Titanium Backup responds eventually to confirm that Root is not available.
c) Downloading from the Playstore is problematic (sometime very slow to download, usually extremely slow to install - go for a walk type of slow!)
d) Typically the pre-installed applications "stop" shortly/immediately after trying to start them (for example, "Browser", "Clock",...), but then appear after "OK"ing the Close infor box
e) Is my choice of ROM reasonable? And/or is there a ROM which has ROOT "baked in"? (Or, should I go back to JellyBean as being more suitable for a Note2?)
f) Is there some "fine tuning" to the flash process that I need to learn about?
Any hints/tips would be welcome, and many thanks for your initial suggestion to move to TWRP

Is the ROM pre-rooted? If yes, don't flash supersu.
You performed a full wipe, including data, before flashing the ROM?
Phone is running these latest bootloader and modem?
Various versions of gapps are here and flash there version that matches your ROM and processor: http://opengapps.org

Many thanks for your further questions/prompts...
a) Yes, I believe I had done a full wipe before flashing, but haven't touched bootloader and modem so they may well be "old"
b) More reading suggests that Cyanogenmod 13 is a very popular ROM, so flashed this with TWRP
c) Found that with this ROM there were no issues when flahsing openGapps
d) Eventually discovered/realised that CM13 is pre-rooted (but has to be enabled in Settings) and that flashing supersu was causing problems
So, with the benefit of hindsight, if I'd used TWRP/CM13/OpenGapps without flashing supersu, it would have been straightforward! I've certainly learned a lot and you supporting questions have led me to what seems to be a nice, stable implementation of Marshmallow - thanks again.
I'm still looking for a quick/easy way to take a screenshot (just used a palm-swipe before), and a free "real" FM radio, but pretty much everything else works.
Great!!!

Glad you got the phone working on CM. We're all here to help and learn from each other.
Last time I looked, which was a while ago, there was no custom AOSP or CM rom that supported radio functions. If you want the FM radio, look into custom ROMs based on a stock Samsung kernel.

Lineage OS 15.0 Dev Thread [DISCUSSION]

Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.

When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?

Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs

Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?

Is there any news?

kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".

Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.

My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.

Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.

hope it will have LOS15.1

Even though Raymon left development does this mean there are no los 15 for us?

As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.

15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.

heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday

heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?

Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.

heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.

https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?

There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.

I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip

Having trouble flashing custom ROM

Hi everyone
I have tried flashing a custom ROM. TWRP3.3.1 is installed and therefore bootloader unlocked. I tried flashing resurrection remix as per this guide:
1)Full wipe (system,data,vendor, dalvik,cache,internal storage) + format data.
2)Flash No-verity-opt patch + xiaomu.eu developer on Oreo or xiaomi.eu 10.2.1 Stable
3)Factory reset
4)Reboot to recovery
5)Flash Resurrected Kernel v3.3
6)Flash POST-sGSI_3_v0.6 .zip
7)Flash RR System.img
8)Flash Magisk 18.0 (if you get an error that /vendor can't be mounted then just reboot recovery and flash Magisk again)
9)Reboot to system
10)Setup system
11)Reboot to recovery
12)Flash BiTGApps or OpenGapps + Magisk 18.0
13)Reboot to system
Although I used Kernel 5.1 PIE
Before this attempt I tried Havoc and I tried lineage and it's always the same... flashing the system.img takes only seconds and declares success. Then the boot screen of the respective ROM stays forever.
I just flashed xiaomi.eu ROM 10.2.1 and that boots fine.
What am I missing here?
Thanks!

Also I don't seem to have anti rollback protection enabled (or I guess I would have bricked the phone anyway by now):
getvar:anti FAILED (remote: GetVar Variable Not found)

Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....

Marco2G said:
Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....
Click to expand...
Click to collapse
Custom Rom development seems to have started very recently after the statement of XIAOMI that there will not be a MAX 4 this year.
But from what I've seen so far, most people are on some kind of MIUI Custom Rom and only a few went the route of trying a more AOSP like Custom Rom.
Regarding your statement that you don's seem to have Anti Rollback Protection, I am 100% sure this is wrong. I've seen threads about that topic that asked why they can't get the ARP value anymore with the method you used and if I recall correctly there was a different way of doing it.
Cheers

I just managed to solve my issues.
I installed the patched TWRP for Nitrogen https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
Interestingly enough, installing a custom ROM image still only takes about ten seconds or so. But now the stuff actually boots.
The Xiaomi.eu ROM that Tradingshenzhen packaged in their tutorial does not have ARB yet. I believe the latest ROMs do.

Look inside your ROM for antiroll the same say to me not found but the beta stock ROM have the 4. This is stopping me to do anything on this phone. Never buy xiaomi again. They add this stupid antiroll they stop betas they make always year after year the phones cheaper.. I mean they remove custom led rgb only white then they make it so small you can't see it. To have the phones cheap they go down on quality

[ArrowOS 10.0] E2001 (Error 7) + despair, frustration

Hello, I really missed the "how to install" section on [ArrowOS 10.0] and got screwed :c
Everytime I try to Install via TWRP I get the "E2001: Failed to update vendor image. Updater process ended with ERROR: 7", and I don't really know what's going on; I saw no TREBLE stuff on this post and went step-by-step on tutorials, but every single time it stops on this error. Actually, afaik having Treble wouldn't be a problem since I came from stock ROM.
The very first time I was on ZUI 4.0.199 and now I'm rolling ZUI 3.5.225 DEV through TWRP (which is the only stock thing I actually managed to install), am I missing something?
It might be something really simple and stupid, so if someone notice it please say it!
I suspect my phone didn't have the 3.5 firmware (which seems to be a requirement), right now I'm searching for the right file to flash.
What I did:
Unlocked Bootloader
USB Debugging
TWRP-3.3.1-0-z2_plus
Didn't go TREBLE or something
Tried wiping everything (Dalvik Cache, System, Data, Cache...)
Reason:
I tried flashing a Custom ROM due to few problems/bugs I had on ZUI 4.0.199 (my phone started rebooting and sometimes it kept rebooting until I charged it). It started annoying me when it kept forgetting WiFi passwords, but since it became almost useless due to rebooting I decided it was time to flash a new ROM and see if I could save my Zuk...
That's how I ended up in this mess, it seemed fairly simply to do but I got lost in the process.

Solution:
Installed 1.9.044 through QFIL, uptaded to 3.5.261 via OTA-Recovery and to 4.0.199 through normal OTA (System Update).
Unlocked bootloader, installed TWRP, did factory wipe and installed ArrowOS 10 (install + cache stuff wipe that appears after installation).
I'll proceed to back up, rooting and mods.
Case closed xD

[Root][CFW][crDroid][MAGISK] How to root / confused about different parts of puzzle!

Howdy!
Please forgive me if this is the wrong place / my google-skills are insufficient!
This is my first post to this forum, because I can't resolve what part is important in rooting (w Magisk?) my RN8P.
First about myself (and my abilities): I did flash some phones (S4 mini, Zenphone2, Yoga Tab 3 plus) with TWRP and Lineage, so basic knowledge should be present, but nothing "in depth"!...
What I did to my RN8P (begonia, global, EU):
OTA-Updated to MIUI A10
Unlocked Bootloader
Reflashed MIUI A9 (because reasons )
Fastboot flashed lk & preloader from CFW MEGATHREAD & non-CFW TWRP
Flashed crDroid (with CFW and TWRP batch) and the crDroid Rom itself w. openGapps via TWRP
What I want to achieve:
Limit my battery charging to a certain percentage
Maybe use the often praised camera app praised with magisk
Let the rest of the system "as is", so have AntiBrick, TWRP and "invisible" Root
Maybe use other magisk-goodies
Versions used:
CFW A10 20200530
TWRP from crDroid-pkg (3.3.1-0)
crDroid 10 20200721 begonia
open gapps arm64 / 10 / pico / 20200730
My question:
I've read about installing MAGISK can trip the AVB, which is to avoid at all costs(?!?), so where is my starting-point for MAGISK?
So what are the pitfalls I have to avoid / consider? / Which guide to follow on how to do it proper?
Forgive my ignorance, any help / bump in the right direction is highly appreciated!

Thoughts so far
Hey!
I think my understanding has grown a little bit...
There is only one Version (no A - A/B) of MAGISK any more, so no fuss about picking the right tool. And being brought via zip-file for flashing within TWRP seems very convenient.
There seem to be TWRP-versions out there, which can mitigate the AVB-tripping for our RN8P, are they CFW compatible? (and which is recommended?)
So basically these questions remain:
Which exact TWRP-version is recommended?
Shall I completely reflash CFW, crDroid, openGapps, when I flash MAGISK? Or just wipe cache / davlik and reset to factory?
Are there other pitfalls or downsides of using MAGISK in my combination of Hard & Software?
Cheers, Mecky85

Not using CFW (Stock MIUI with Magisk benefits), but here is some advice:
0. Make sure you follow every step on TWRP site (especially the vbmeta flashing part). It can save you from headache. I don't say you have to use TWRP, tho. Also make sure you do this step if you return to stock boot image. Do it once, and you are fine.
1. Use CFW-compliance recovery, as recovery has it's own firmware.
2. In my case (I'm doing update with this procedure: MIUI+Magisk>vanillafy>update MIUI>Mod), no need to reset anything. But resetting dalvik+cache is not bad either.
3. Out of question.
Hope that help.

Thanks for the headsup with vbmeta, will have time to look (and hopefolly have a got at it) after the weekend!
Will post my experiences in here.

After a good batch of reading into the topic... I'm not convinced any more I'll cope with it...
Not worth for me to figure everything out, if reading into this is such a hassle... :silly: