yashsingh1/xdaforums huggingface dataset:
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] PeterMarkoff:
i am using berkeley, had pretty much unusable Wi-Fi dropping each minute although it could be caused by dirty flashing Berkeley and Charlotte back and forth, so started again from scratch and stick with Berkeley build, GZR zero gapps (but soon will get rid off gapps completely, just need to figure out photo backup other than Flickr instead of photos) and Huawei camera from OP, magisk newest beta 16.7 with newest MM, occasionally some apps stopped but other than that haven't really noticed any issues, currently also using with notch without hiding it, didn't like black bar covering content of some apps

i have Bluetooth always on and my Amazfit Bip notifications work fine immediately, not listening through Bluetooth (using speaker Creative Chrono) that much but never experienced any connection issues

btw don't thank here, I did nothing, if you want to thank someone head to original Luk's threads
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] franky14:
Stop spamming the same on all Honor 10 posts.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] ulkika:
you have to forgive me if I disturb you was not my intention to feed but I hoped that at least in an article in 5 someone answered me on the utility of asking the code and do the Root when in any case you still have no operating system that works better than the original I have no kernel that is able to overclock or make battery consumption more functional
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] ivanwong1989:
I don't need all that. I root because I want to be able to control when i doze. I want to be able to screen lock without timeout using double tap.

Everybody got different reason. Can't get better ROMs doesn't mean everyone should give up rooting. They got their own reasons
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] kiritoxd:
can someone help me cause after i wipe my data and cache and system i rebooted my phone(idiot) now my phone wont boot into recovery.stuck in recovery for so long...wont go into bootloader but i made a twrp backup but i cant restore as i cant get into twrp can someone help me with this asap thanks alot:rolleyes:
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Longerski:
Why you can not get into TWRP?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] kiritoxd:
idk keeps on loading but for some reason all is well now after like trying to get into the bootloader after so many times it works but i had to revert to stock and install the stock recovery
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Longerski:
I don't understand to you.

Odesláno z mého Honor View 10 pomocí Tapatalk
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] PeterMarkoff:
updated to build 20180925, dunno changelog, I don't see any new issues
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Drakorcarnis0:
I will try when I've a bit of time !

Edit: I'm currently on 9.0 beta vendor. Do you think I need to roll back to 8.1 ?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Thiphariel:
I'm interested on downgrade to 8.1 tho.. If you have some ways, I'll take them :)
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] H3artbrok3n:
Is there a way to install this without TWRP?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] WhiCCX5:
Thank u sincerely.

By now are these bugs sitll exist?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
It is possible to make a twrp full backup and then restore that backup if I wanna go back from a custom rom?, I want to be sure if this modification of twrp supports that feature.

One more thing. Do I need to be in a specific firmware version?, I'm in .163 and want to know if I need to downgrade to a specific version in order to work properly.

Thanks in advance :)
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] liujunyu29682776:
:highfive:
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] k_web9000:
I stayed away from custom ROMs until now after trying this the last time I posted. Spotted your update and figured I'd give it another go.

I installed the latest build from scratch, the latest GZR Zero apps, magisk 16.4 and this camera port.

So far everything seems to work smoothly. No issues whatsoever that I've discovered thus far. Bluetooth is fine now compared to the drops before. Audio works great. Camera all seems working... touch wood etc.

I'll update if encounter any issues but this seems like it should be daily-driver level for me for now.

Update: So far everything still seems to be working as it should. I do get audio dropout of Bluetooth here and there after all but only very rarely if I'm doing something seriously network intensive at the same time. It almost never happens now compared to every time I loaded anything in the background. Literally the only other bug is an occasional problem with Google assistant where I can't dismiss it from notifications without force closing the app but that could be on their end not mine.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] mgs250:
This rom is surprisingly working very well for the last few hours. Hope to have some pie builds soon! Thank you for you work [MENTION=5897346]PeterMarkoff[/MENTION] :D
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] fosterqaz11:
Don't know about first part but you don't have to worry about firmware Version.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
Can you share the link of that rom, please?

---------- Post added at 07:15 PM ---------- Previous post was at 07:10 PM ----------

Can you share the link of the AOSP of oreo?, does support notch?, anny issues?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
Anyone with a Chinese variant that can confirm this rom works?, I don't event have AL version, I have TL10
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] fosterqaz11:
Probably should work since it is a custom rom not country generic firmware
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
I'm just asking because sometimes the phones have differences, for example international versions and regional versions. In this particular case, I think it's just the ram difference (6 and 4) and LTE bands.

I just wanted to be sure. I'll give it a try if I can get a bootloader unlocking code, someday :'( hahaha
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] fosterqaz11:
And that will be forever I guess haha
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
I sent a request in the XDA form a couple months ago, but I'm still waiting for the code. Hopefully I'll get it before the end of the year. If I don't have any luck by then, maybe I'll switch to the pixel 3 or Xiaomi mi 6 with AOSP (because I like small phones)
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] H3artbrok3n:
Nice rom, tho i reverted back to stock rom after 2days of usage.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] kenerly:
Would you mind updating the post with the newest version "lineage-15.1-20181011_115020-UNOFFICIAL-berkeley.zip"

I tried to edit it but I'm getting invalid zip in twrp.

Thanks

---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------

Just goto https://funkyhuawei.club/buycodes

I did it, cost me $55, had the code in 3 hour.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] FranekOz:
Hey man,

Did you try maybe to flash any other time from Berkeley? There are some pie ROMs for ex. And of course spec. is quite the same. Anyway good work :)
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] UncleTony:
absolutely :o:svetius:
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] FranekOz:
I wanted to flash something on my honor few days ago. But im totally moron, didnt request for unlock code :')
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] StuDB:
Did you ever get a code?

I requested mine and never got any contact. I'm guessing I'll never get it now :crying:
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] PeterMarkoff:
those Pie ROMs require EMUI9, so if you have this ROM it's PITA and not really sure if it's worth, personally I don't see Android Pie appealing at all and would not mind buying brand new phone with Oreo instead
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] FranekOz:
I have EMUI9 actually. Anyway for now I cant do nothing. I missed to apply for bootloader unlocking code (I was quite busy). It's really sad. Any contact with Huawei and honor help center is something like " we aren't providing codes because lot of users failed and damaged their phones". And nothing else :) I think they should do some exams for iq test or some while u are applying for code ?. It's looking like I have to wait until maybe XDA will make that event again.
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Jab_:
Nope, unfortunately, same here :/
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] StuDB:
Hey, PM'd one of the XDA members. Sounds like codes might still be issued :good:

Not guaranteeing you'll get one but definitely not bad news!
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] mlhkrts:
Hey guys its working on Honor 10?

COL-L29
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] Appelkoekje:
Who can you message?
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] StuDB:
I messaged the OP from the code discussion. Messaged again and was told it's up to Honor so no idea if they'll ever be given out..
[Honor 10 ROMs, Kernels, Recoveries, & Other Develo] #chester#:
do not ask the project;)
[Touch Cruise ROM Development] ariebk:
is there a way to disable the smat dial in WM6.1 ?

i just can't find it ...
[General Questions and Answers] go vegan:
My adoptable SD-card took a crap.

I'd like to think that I can recover the password/key (with a rooted phone), use ddrescue to make an image of the card, use the password/key to decrypt the image of the card, use fsck to fix the file-system (it's ext4, right?) then copy the repaired image back to the card and have a nice day.

Or maybe there's way to fsck the card in the phone? (after making a backup image)

Is this possible? Is there another way to un-screw a corrupted SD-card that's used as adoptable storage?
[General Questions and Answers] Droidriven:
If you're trying to fix it so that it works "as-is" again, I wouldn't put too much faith in that.

You can recover the data on the sdcard by various methods, there are many methods and tools, such as these:

http://www.rescuedigitalmedia.com/retrieve-files-from-sd-card-formatted-as-internal-storage

There are more in depth and technical methods/tools also.

Once you have your data safely recovered, format the card and try replacing your data and setting up adoptable storage again the way you did originally.
[General Questions and Answers] go vegan:
Using this as a guide for key recovery and data decryption - https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html

1- Make a backup of the card

ddrescue -n /dev/sdc bad-card.img bad-card.log

ddrescue completed in one pass with zero errors. Nice. From here, I'm working with a BACKUP of the card, NOT the card itself.

2- See what's on the card

fdisk -l bad-card.img

Output:

Disk bad-card.img: 120.3 GiB, 129116405760 bytes, 252180480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Device Start End Sectors Size Type
bad-card.img1 2048 34815 32768 16M unknown
bad-card.img2 34816 252180446 252145631 120.2G unknown

3- Copy the 2nd partition to a file

dd bs=512 skip=34816 if=bad-card.img of=bad-card-p2.img

* Your numbers may be different

4- Using the encryption key I found using the link, above, mount (read-only) this (2nd) copy of the card

losetup -r -f --show bad-card-fs-p2.img

cryptsetup luksOpen /dev/loop0 bad-card-fs-p2.img

dmsetup create crypt1 --table "0 252145631 crypt aes-cbc-essiv:sha256 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 0 /dev/loop0 0"

mkdir /tmp/mount1

mount -o ro -t ext4 /dev/dm-4 /tmp/mount1

* Your numbers may be different

nb, the "4" in "/dev/dm-4" can be identified by the minor device-number here:

dmsetup info crypt1
Name: crypt1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 252, 4
Number of targets: 1

Boom! My files are there!

From here, I used dd to make an unencrypted copy (as a disk-image file) and ran fsck on it. It fixed a few things, apparently nothing catastrophic.

Yeah, recovering pictures and music and that stuff wasn't too bad (since the device is rooted and I was able to recover the encryption key) but getting back the apps and getting the phone back to the state it was in a few hours earlier is not so straightforward.

Lesson learned: Keep a backup copy of the encryption key (in a safe place) so that data can be recovered from an "adopted" SD-card even if the phone gets smashed by a rock.

Too bad there isn't a way to do a "bare metal" backup of an android.
[General Questions and Answers] Droidriven:
Very nice.
[General Questions and Answers] go vegan:
Same thing happened again. I knew I'd left a how-to here, so using this as a guide I fixed it much quicker, this time.

1- Power-down and remove the "corrupt" SD-card.

2- Use ddrescue to make a backup copy of the card

ddrescue -n /dev/sdg bad-card.img bad-card.log

That ran with no errors.

3- While that was backing up, I booted into TWRP and copied expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key to a flash drive via OTG. That's "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key", as per - https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html

4- After ddrescue was finished, I decrypted the SD-card.

blockdev --getsize /dev/sdg2
249702367

od -t x1 expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key
0000000 yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy
0000020

dmsetup create crypt1 --table "0 249702367 crypt aes-cbc-essiv:sha256 yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy 0 /dev/sdg2 0"

5- Find out what "crypt1" links to, and what it is.

file -s /dev/mapper/crypt1
/dev/mapper/crypt1: symbolic link to ../dm-5

file -s /dev/dm-5
/dev/dm-5: Linux rev 1.0 ext2 filesystem data, UUID=aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa (extents) (large files)

6- fsck /dev/dm-5.

fsck /dev/dm-5
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/mapper/crypt1: clean, 14314/7806976 files, 21089519/31212795 blocks (check after next mount)

7 - "Remove" the SD-card.

dmsetup remove crypt1

8- Put the card back in the Android, and it's all good.

nb - Turned out that I didn't need a copy of the card, but it's still good practice to make a backup.
[General Questions and Answers] nyckwilliams:
You are going to big trouble if the card is not recovered.
[General Questions and Answers] Droidriven:
Did you even read the thread? This member not only posted how they solved the issue but has had to do it twice and posted about it a second time just above the post you made.

Learn to read more than just the first few posts or first few pages of a thread.
[General Questions and Answers] go vegan:
Note to self (and everyone else who finds this) to make it easier to work with image-files from SD-cards. Make use of losetup's "-P" flag to automatically create partitions.

losetup -r -f --show [B]-P[/B] bad-card.img
/dev/loop0

ls -lh /dev/loop*
brw-rw---- 1 root disk 7, 0 Aug 30 09:31 /dev/loop0
brw-rw---- 1 root disk 259, 0 Aug 30 09:31 /dev/loop0p1
brw-rw---- 1 root disk 259, 1 Aug 30 09:31 /dev/loop0p2
...

Now, the partition of interest is set up as "/dev/loop0p2" with minimum fuss.
[General Questions and Answers] Future Technation:
Easy, sure and fast solution!

Hello everyone!

I'm going to give you a wonderful news!

You do not need to follow these complicated instructions that are still useful to know in case of need and thanks for this.

The solution is much easy and that's it:

Without turning off the smartphone, remove the micro SD card and reinsert it again.

That's all! ;)

This solves your problem!

Good Android to everyone.

Android 8.1 with Lineage OS on Samsung Galaxy S5 klte and micro SD 128 GB extreme SanDisk A2 U3 V30
[General Questions and Answers] go vegan:
1- First, make a backup.

2- Good luck.

3- Does that work if the SD card was not unmounted/ejected properly, and the file-system is marked dirty?
[General Questions and Answers] Future Technation:
Hello Vegan,

the problem mentioned is created precisely because the system has failed to mount the micro SD and identifies it as corrupt, but it is not really so.

Simply the system has not mounted it and is therefore inaccessible! (Of course, at this stage everyone takes the panic for their data :eek: :crying: ).

In my specific case the micro SD is the main memory and obviously also has all the data.

Since it is not yet mounted in the system (due to a reading error), you can not back up your data on the micro SD card.

Furthermore, since it has not yet been mounted (due to a reading error), it can be safely removed and reinserted without restarting the smartphone.

Once this is done, everything is fine.

I hope I was clear in the explanation.
[General Questions and Answers] Droidriven:
I'm not sure this applies to the specific situation that the OP posted about.
[General Questions and Answers] go vegan:
In my case, the file-system was marked "dirty" and thus could not be mounted by the OS until after it was fsck'd.
[General Questions and Answers] Future Technation:
Hi Droidriven,

it's exactly the same situation, I confirm it.

---------- Post added at 12:02 PM ---------- Previous post was at 11:06 AM ----------

Hi Vegan,

I had exactly the same problem, the filesystem was corrupt, I explained it well on my post. The micro SD works only after removal and re-insertion. There is no need for check disk. What you did was your option and choice, but in this specific case it is not necessary. You probably did not do as I described but you immediately removed the SD card for a check disk. This post can help many people. Why complicate things when the solution is so easy? Less experienced people can panic. Our job is to help and simplify the work, not to complicate it. However, I'm sure you did your best to solve your problem, but this solution has to admit that it's much easier for everyone.

Have a nice day.
[General Questions and Answers] Droidriven:
Well...

You see...

I'm willing to bet that they tried that first, since it IS the first and simplest troubleshooting step for the scenario, even a noob would know to try that and they seem to be a bit more advanced than a noob. You post as if they did not try that kindergarten level troubleshooting step first, which I'm sure they probably did. But I could be wrong.
[General Questions and Answers] Future Technation:
Hi Droidriven,

This proves that he did not do it.

The fear factor can always affect one's choices.

Please, review my posts well, I gave a technical and exhaustive explanation of what happened and why I did it that way.

In any case my solution is valid and working. Those who present the same problem can take advantage of this information.

Have a nice day!
[General Questions and Answers] Droidriven:
That doesn't prove that they didn't remove and reinsert the sdcard, though. That just proves that their sdcard wasn't working. Nothing in what they posted says that they didn't remove and re-insert the sdcard, you're assuming they didn't because removing and reinserting worked for you. This assumes that their sdcard was "corrupted" for the same reason that yours was and in the same way.

I'm not disagreeing that your method worked for you, I'm just saying that your scenario and their scenario are not necessarily the same.
[General Questions and Answers] Future Technation:
Excuse me but how old are you? You are a child? This would explain all these controversies. You always want to have the reason anyway. Even if you were an adult, you behave like a child! I have no time to waste with you, but willingly with those who really need to solve the same problem! Those who are truly experts will appreciate this solution. You are spamming here. I will not answer you again. Goodbye!

--------------------------------------------------------------------------------

Hi Go Vegan,

I want to apologize with you for this little discussion, because I started quoting you. My intent is always to share something useful for others. Thank you for your intervention, because obviously if my first approach to this problem does not work for someone, yours becomes indispensable, as obviously it has already been certainly for many others.

This words are for everyone: "We must learn to really listen to others before answering".

Have a nice day!
[General Questions and Answers] go vegan:
Might also depend on the phone, the ROM, the version, etc. Might also depend on whether the card is "internal" or "external" storage.
[General Questions and Answers] Droidriven:
Actually, with the way you are defending yourself when I'm just telling you the truth, that makes you appear as the child.

You have only 5 posts here and just joined a few days ago. This tells me that you probably haven't dealt with android devices enough to know there can be many different causes for the exact same issue, even on two identical devices that show the same symptoms and that what works in "this" situation on "that" device, doesn't always work the same for another device with the exact same issues.

I was just saying that there are many different details that make all the difference in the world. It's obvious, from everything that you have posted here, that you are unaware of those facts. I was just trying to tell you that you can't be so certain that what you posted is the fix for every user and every device that has this issue. Dont take it so personal.