seeing all of you people with unlocked bootloaders is making me jealous, i paid like 5 times more for one euro for DC Unlocker, still didn't unlock my bootloader. Life sucks, man.
HUAWEI Y7 PRIME (2018)/NOVA 2 LITE/LDN-LX2/LDN-L21/LDN-TL10 General Discussion
- Thread starter Nomorenoless
- Start date
-
- Tags
- huawei-y7-prime
New version of Descendant GSI is released:
Descendant XI, Android 11, ARM64, A-only official (1.4 GB).
Mod edit - translated by https://translate.google.com/?:
Brother, I said Chinese, will you brush MAGISK will not card the first screen?
********************************************************
兄弟，我就说中文了，你刷magisk会不会卡第一屏？
Last edited by a moderator:
Well, do NOT expect Harmony OS for our devices. Last EMUI 8.0 update was 13 months ago.
www.huaweicentral.com
HarmonyOS (Hongmeng OS) Eligible Devices
At Huawei Developer Conference (HDC) 2020, Huawei announced HarmonyOS 2.0, which supports more platforms compared to its predecessor. According to the official roadmap, HarmonyOS 2.0 will support devices with up to 128MB RAM, such as smart wearables and other IoT devices. In 2021, It’ll support...
www.huaweicentral.com
I solved the problem,you could use magisk which built by phh.
我解决了这个问题，你可以用phh的magisk。
There's another problem. When I brush the GSI of Android 11 and 9, there's a problem with the brightness. The maximum brightness is still very dark. Android 10 is normal. Do you have any solutions?
还有个问题，我刷安卓11和9的gsi，亮度有问题，调到最大亮度还是很暗，安卓10行正常，你有什么办法解决吗？
My mother in law's LDN-LX2 started acting up recently, it starts and after a few seconds of home screen it restarts again. Its like a boot loop but it actually loads homescreen and I can manage to go into settings to uninstall apps. Anyone heard about this issue? Phone keeps rebooting after 30seconds to one minute of ON time. I opened it up and cleaned all the terminals inside etc. I don't want to flash it with a factory firmware so she doesn't loose whatsapp(shes visiting from another country and wouldnt be able to activate whatsapp).
Thanks
Thanks
At least, she can freely wipe /cache partion from eRecovery menu (3rd button, 2nd is Factory reset). It seems at something pressing on touchscreen or power button (foil or silicon mask or even magnet, if she using fold cover). Also, you can disable all options in Settings - Accessibility.
New custom recovery - OrangeFox R11.1
Flash *.img to recovery_ramdisk partition in fastboot mode or via custom recovery.
Copy Fox folder to the root of internal memory (sdcard in custom recovery, /storage/emulated/0 in system).
Flash *.img to recovery_ramdisk partition in fastboot mode or via custom recovery.
Copy Fox folder to the root of internal memory (sdcard in custom recovery, /storage/emulated/0 in system).
Hi,
I made a mistake. Instead of writing rm -r vendor/* i wrote rm -r vendor. This has deleted my vendor folder. I have recreated it using mkdir vendor but i am unable to mount it in twrp. I flashed vendor image and system but phone is in bootloop
Please tell me a solution
I made a mistake. Instead of writing rm -r vendor/* i wrote rm -r vendor. This has deleted my vendor folder. I have recreated it using mkdir vendor but i am unable to mount it in twrp. I flashed vendor image and system but phone is in bootloop
Please tell me a solution
1 - Had you flashed vendor via fastboot? ( fastboot flash vendor vendor.img )
2 - Can you boot into twrp ?
Since /vendor is symbolic link, you need to flash vendor image to /dev/block/mmcblk0p51.
Or even full path /dev/block/platform/soc/7824900.sdhci/by-name.
You can do it from twrp, terminal as superuser (su) via dd and vendor image on sd card >
dd if=/external_sd/vendor.img of=/dev/block/mmcblk0p51. Also try to flash dm-verity + forced-encryption patch.
3 - You can probably boot to eRecovery to recover latest stock system. Also flash the same patch with twrp and permissive kernel.
Yes i can boot into twrp.
I used dd command interminal to copy vendor.img to /dev/mmcblk0p51 but vendor is unable to mount. Then i flashed vendor to vendor image still unable to mount vendor. Then i created symbolink by using "ln -s /dev/block/mmcblk0p51 vendor" it is still unable to mount
Update:
i have solved the problem by flashing full stock rom.
..
And please provide me the link of dm-verity+force encryption remover file
Update:
This is solved by flashing gaguga3.img and clicking fix encryption in advanced/tools
I used dd command interminal to copy vendor.img to /dev/mmcblk0p51 but vendor is unable to mount. Then i flashed vendor to vendor image still unable to mount vendor. Then i created symbolink by using "ln -s /dev/block/mmcblk0p51 vendor" it is still unable to mount
Update:
i have solved the problem by flashing full stock rom.
..
And please provide me the link of dm-verity+force encryption remover file
Update:
This is solved by flashing gaguga3.img and clicking fix encryption in advanced/tools
Last edited:
Now my phones current vcersion is 8.0.0.166. when i flash permissive kernel phone struck in bootloops.
Update:
That is solved by adkcal.img in kernel
Update:
That is solved by adkcal.img in kernel
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I don't have current screenshots/video of custom roms on my LDN-LX2 but I do have old pictures of it.Thank you for information.
Do you know about this rom video or screen shot if there is?
-
2Huawei Y7 Prime (2018) is a phone that packs 6 inches HD+ Fullview IPS Display with Qualcomm Snapdragon 430 and 3gb of ram/32gb of internal storage. It has a dual camera setup of 13+2mp 2,2 aperture and a front camera of 8mp 2,0 aperture. This phone was released April, 2018 and has Android 8.0 onboard with a kernel that is attached in here. I ask for a cooperation with XDA developers and I hope that we, users, help you as well in return. I hope that these device will soon have its custom recovery, root guide, custom kernel, and etc.
This is the link for its kernel source code, "LDN" is the name of the device: http://download-c1.huawei.com/downl...oadId=98800&version=416724&siteCode=worldwide
I hope for a better future with this phone I'm using:fingers-crossede32::cyclops:
22Sorry for replying late! Had some few examinations to go through before continuing some android development. I'll answer some questions since my last visit here.
I'll see what I can do about that. Meanwhile, feel free to use @adeii 's solution here.
That might be a good solution to the boot-up failure we've been getting on Pie GSIs.
Also, I need your favor, since you're still on stock rom (and most probably rooted), could you upload framework-res.apk from /system/framework? The max brightness on my GSI is literally the minimum brightness on the stock EMUI rom. I need the file to create and overlay file(which has info about the true minimum and maximum brightness for the device). If you wanna know more about what I mean, here it is.
Hmm, I would recommend phh-treble by @phhusson if you're upgrading to a Pie GSI. And this is the ONLY GSI that would work on the device as of today's testing.
For Oreo GSIs, you're better off with any GSI you'd like since I tried 5 and they all would boot.
Just make sure you've done:
- Filesystem modifications (would ease some installs on TWRP/remove forced encryption)
- The permissive kernel I made. (Since GSIs need a permissive SELinux to boot)
- a full wipe (system, userdata, cache)2After a bunch more testing....
CC: @adeii
Ok, I’ve tested the permissive kernel and it works fine on @phhusson’s Android Pie GSI. What I’m weirded out is that it doesn’t want to boot any other GSI out there.
Resurrection Remix needs to be flashed over phhtreble to actually boot, but the kernel init stage takes TOO MUCH TIME.
If you want to try, this is the method:
Then, do the initial setup. After finishing, reboot to fastboot and do this:Code:fastboot erase system fastboot flash system (phhtreble GSI) fastboot reboot
The -u is needed to flash over phhtreble system files, more accurately merge them both.Code:fastboot -u flash (RROS 7 GSI) fastboot reboot
Be careful: This results in ADB and SD Card not working, and the kernel init slowness. (This is not all the bugs I found since I quickly reverted back into phhtreble)
Luckily, I might have a solution to the problem. The main problem would be that the vendor HALs (the piece of android code used to communicate with /vendor code) that are present in any other GSIs support Huawei’s EMUI 9 vendor HAL but not EMUI 8 vendor HAL. One proof that this might be true would be this repo by @phhusson himself which contains a folder called “Huawei-8.1” which the latest commit (as of writing) labelling it as EMUI 8.1 HALs. What’s convenient about this repo is that it has an automatic GSI builder with device patches which enable booting on other devices (in this case, the LDN device line). I’ll fire up my android build server and see if this method works.
If you want a build of these GSIs below, let me know. I’ll build one for you.
I’ll do some further testing, will be back with you guys in about 3-4 days of tireless backups and tests. Feel free to send me PMs if you want, I’m in the forum in like 7am - 9am, 12pm - 2pm, and 10pm - 11pm (all times are in UTC btw). See ya!
Screenshots of phone running Android P:
https://imgur.com/a/JH9VFQt
https://streamable.com/vavpm2
Does sourcecode contain /kernel, /vendor folders only or you had found something more like device tree?
This should be enough to make custom recovery first, but for custom rom...something is missing.
