REMOVED PROJECT
XDA:DevDB Information
AOSP For The Honor 6x, ROM for the Honor 6X
Contributors
Meticulus
Source Code: https://github.com/Meticulus/android_kernel_huawei_hi6250_4.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 5.X
Based On: AOSP
Version Information
Status: Testing
Created 2017-12-03
Last Updated 2018-01-18
Installation Video....
Woaaahhh..
New rom...volte working ??? Thats d only thing i want to work in my phone properly as calling is so important in my career right now
Wow something exciting cooked..5 ROMs in 2 days after so much time that's great indeed.
Hats off to all for this work.
sreekantt said:
Woaaahhh..
New rom...volte working ??? Thats d only thing i want to work in my phone properly as calling is so important in my career right now
Click to expand...
Click to collapse
I am uncertain of this. If you have time, please give this a try and let us know...:highfive:
shashank1320 said:
Wow something exciting cooked..5 ROMs in 2 days after so much time that's great indeed.
Hats off to all for this work.
Click to expand...
Click to collapse
Honestly, I do not own an Honor 6x. The code base was developed for the P9 lite but we discovered that it worked with many other hi6250 devices. We know this ROM works for this device because @felix-development tested it.
Nice work and good rom. Keep Updating
sreekantt said:
Woaaahhh..
New rom...volte working ??? Thats d only thing i want to work in my phone properly as calling is so important in my career right now
Click to expand...
Click to collapse
Great news , ...are you sure about volte ...
HebrArtin said:
Great news , ...are you sure about volte ...
Click to expand...
Click to collapse
He is asking it mate..if VOLTE works, he will flash as he need this feature.
What bugs?
I can't flash it "This package is for hi6250" devices; this is a "berlin"
nice, clean & smooth
algg said:
I can't flash it "This package is for hi6250" devices; this is a "berlin"
Click to expand...
Click to collapse
What TWRP are you using?
Meticulus said:
What TWRP are you using?
Click to expand...
Click to collapse
twrp 3.1.1-0
maybe to add I was on stock emui 4 (marshmallow) when I got the device, since there appearently were no official updates I manually flashed the emui 5 nougat and now tried to flash this.
btw I also read the install instructions on their site but I thought it would screw my device since the recovery is actually made for another device
algg said:
twrp 3.1.1-0
maybe to add I was on stock emui 4 (marshmallow) when I got the device, since there appearently were no official updates I manually flashed the emui 5 nougat and now tried to flash this.
Click to expand...
Click to collapse
Try my TWRP : http://www.meticulus.co.vu/p/twrp-for-huawei-p9-lite.html
I booted into fastboot flashed it like I did the previous twrp.
Then I rebooted while holding power up (this is how twrp started) and got into Huaweis erecovery menu.
Then I booted the actual OS and tried to boot the custom twrp through adb.
It did reboot but again went into the erecovery menu.
Is this a fault on my part or simply incompatible devices? I used the emui 5 twrp since I am on emui 5 but again the stock rom delivered for my device was emui 4.
Am I actually supposed to flash the entire Zip file at once (fastboot flash recovery file.zip) or do I have to manually extract the file and then flash every single file individually?
While flashing the zip fastboot said it was succeful
algg said:
I booted into fastboot flashed it like I did the previous twrp.
Then I rebooted while holding power up (this is how twrp started) and got into Huaweis erecovery menu.
Then I booted the actual OS and tried to boot the custom twrp through adb.
It did reboot but again went into the erecovery menu.
Is this a fault on my part or simply incompatible devices? I used the emui 5 twrp since I am on emui 5 but again the stock rom delivered for my device was emui 4.
Am I actually supposed to flash the entire Zip file at once (fastboot flash recovery file.zip) or do I have to manually extract the file and then flash every single file individually?
While flashing the zip fastboot said it was succeful
Click to expand...
Click to collapse
Oh geez man. You did NOT flash a zip file via fast boot did you? Zip files should never be flashed via fastboot. There are installation instructions @ the link I gave you. Did you see them?
Hey sorry but does this have (LTE - HwC) and does it work on Model : BLL-L21 , because if we don't get oreo i'll totally flash this ROM and thanks
Sorry yea that was my fault. I completely missed that line for some reason.
I flashed the recovery and used it to flash the image. Everything worked and now I rebooted but like all other ROMs I flashed yet (expect the one official emui rom) it gets stuck during the boot animation.
I have waited up to 30 minutes on different roms during the boot animation but literally nothing happens. Is this a fault on my part or can the device be somehow faulty?
Mind me but I am not really expierenced with Android.
It's around 20 mins now and it still is stuck at the "android" boot logo. After a factory reset the stock rom takes around 5 minutes to boot.
CodingAddict704 said:
Hey sorry but does this have (LTE - HwC) and does it work on Model : BLL-L21 , because if we don't get oreo i'll totally flash this ROM and thanks
Click to expand...
Click to collapse
yep , can you please tell if hwc bug has been fixed or not?
Related
My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:
MIUI 7.2.1.0 without firmware update.
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
I hope you can make modified rom 7.2.1.0 without bootloader.
ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
welcome aboard, my dear friend!
Looks to me, we got another developer. Good
ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:
ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:
I want to flash an RR into my Mi 4C. So I unlocked my bootloader by registering in Mi.com.
Firstly I flashed in a TWRP Rec
Code:
fastboot flash recovery ..../twrp.img
fastboot boot twrp.img
And successfully boot into rec.
Then I tried to install the ROM. After flashing it stuck on the Mi Logo every time.
Tried sideload and "install" by the TWRP but didn't work.
You can simply check your bootloader status by
fastboot oem device-info
Click to expand...
Click to collapse
Also select correct TWRP version for Mi4c, based on android version
Suxter said:
You can simply check your bootloader status by
Also select correct TWRP version for Mi4c, based on android version
Click to expand...
Click to collapse
TWRP selection is related to Android version? Could you please explain a little? When I was flashing my Nexus 6P I've never considered about Android version
Darkouting said:
TWRP selection is related to Android version? Could you please explain a little? When I was flashing my Nexus 6P I've never considered about Android version
Click to expand...
Click to collapse
After you flashed Nougat based Xiaomi rom, you can't boot on the older version of TWRP.
There is a new TWRP for nougat rom.
If you already flashed Nougat based Xiaomi rom, use the new version. You can find it in here https://xiaomi.eu/community/threads/7-2-16-17.38651/
Suxter said:
After you flashed Nougat based Xiaomi rom, you can't boot on the older version of TWRP.
There is a new TWRP for nougat rom.
If you already flashed Nougat based Xiaomi rom, use the new version. You can find it in here
Click to expand...
Click to collapse
Nothing ever changed
I used this TWRP before.I flashed it in, boot the recovery, flashed in my ROM, checked clear Dalvik cache, pressed Reboot System.
The screen goes dark and never turned on. Press the power button only to realize it Reboot into bootloader.
Every time I reboot it reboot in Bootloader.
Plus I do a FULL wipe every time I flash in and did not work ?
UPDATE!! I flashed in a ROM in XIAOMI.EU and succeed.But why ???
Still failed in flashing in other ROMs
Darkouting said:
Nothing ever changed
I used this TWRP before.I flashed it in, boot the recovery, flashed in my ROM, checked clear Dalvik cache, pressed Reboot System.
The screen goes dark and never turned on. Press the power button only to realize it Reboot into bootloader.
Every time I reboot it reboot in Bootloader.
Plus I do a FULL wipe every time I flash in and did not work
Click to expand...
Click to collapse
sorry to here that then. which MIUI version you flashed? official & unofficial ?
Suxter said:
sorry to here that then. which MIUI version you flashed? official & unofficial ?
Click to expand...
Click to collapse
xiaomi.eu provides a modded MIUI. Maybe it's unofficial.
I got a weekly-update version and flashed it in and succeed.
It is MIUI 8
Darkouting said:
xiaomi.eu provides a modded MIUI. Maybe it's unofficial.
I got a weekly-update version and flashed it in and succeed.
It is MIUI 8
Click to expand...
Click to collapse
try this.
flash this http://bigota.d.miui.com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz with MiFlash
then connect to fastboot & fastboot oem unlock
now flash TWRP for 5.1 rom https://www.androidfilehost.com/?fid=24421527759888487
boot into TWRP & install any other rom.
for nougat based xiaomi.eu rom, read their introductions carefully https://xiaomi.eu/community/threads/7-2-16-17.38651/ Don't flash TWRP for nougat rom if you still in 5.1 ( TWRP for nougat https://www.androidfilehost.com/?fid=457095661767135741 )
Suxter said:
try this.
flash this http://bigota.d.miui.com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz with MiFlash
then connect to fastboot & fastboot oem unlock
now flash TWRP for 5.1 rom https://www.androidfilehost.com/?fid=24421527759888487
boot into TWRP & install any other rom.
for nougat based xiaomi.eu rom, read their introductions carefully https://xiaomi.eu/community/threads/7-2-16-17.38651/ Don't flash TWRP for nougat rom if you still in 5.1 ( TWRP for nougat https://www.androidfilehost.com/?fid=457095661767135741 )
Click to expand...
Click to collapse
It worked! So that seems to be a bug that only exists in my 4c on MIUI based on Android 7.0 ?
THANKS A LLLLOT！
Darkouting said:
It worked! So that seems to be a bug that only exists in my 4c on MIUI based on Android 7.0
THANKS A LLLLOT！
Click to expand...
Click to collapse
Most probably you mess up with old TWRP & Nougat 7.0 rom
You are welcome :good:
Thanks dude! It helps me a lot! I thought we need to install Nougat recovery before flashing Nougat rom!
Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?
RAHUL3387 said:
Is it possible to flash twrp in honor 6x BLN-L22 Android version (Nougat 7.0) ?. Have tried to flash it using fastboot, after that my device is stuck in "your device is booting now" screen, Is it possible?
Click to expand...
Click to collapse
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
hassanjavaid8181 said:
Yes its possible to flash twrp...
What error it gives while you try to flash twrp...
What version. Of twrp you used??
Click to expand...
Click to collapse
Thank you so much for responding. It doesn't give me any error while flashing it, going to bootloader using cmd and fastboot flash recovery twrp.img, it shows ok successful but after that i entered fastboot boot twrp.img... it's stuck in your device is booting now. I have used every available twrp in official website.. American and European ones. Nothing worked.
RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
Thank you so much for responding. Will try and get back to you with the result.
RedSkull23 said:
It is possible that it doesn't boot, and... This happens if you flashed the TWRP available on official TWRP site (I remember that, it happened to me also).This is because they've uploaded a version that doesn't work with our device (it's there from months now, i don't understand why it is still there... I have to report that), but no worries; you can solve this easily flashing the OpenKirin version of TWRP that you can grab here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 flash it via fastboot like you already did with the actual TWRP, and you're ready to go. I tried it on different builds, it always works and i still thank OldDroid's work on it for making TWRP working on Honor 6X.
Click to expand...
Click to collapse
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.
RAHUL3387 said:
It worked :laugh: Have been working on this for three days. It's true TWRP which is available officialy is not working. Thank you so much man.
Click to expand...
Click to collapse
Nothing hard to do dude, the important is that it works now
Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!
On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method
Rayan19997 said:
On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method
Click to expand...
Click to collapse
The custom ROM was Linageos 14.1, so it wasn't anything EMUI based.
I'm gonna try and manually flash the ROM from an update.app that we downloaded from the app Firmware Finder.
ZelafAry said:
Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!
Click to expand...
Click to collapse
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??
hassanjavaid8181 said:
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??
Click to expand...
Click to collapse
We did not make a twrp backup (In hindsight we should've....)
We don't have twrp on it right not but can be fixed if needed.
We were on the latest update available to the phone which should be latest today as well. (OTA)
Flashing it manually made the phone enter a bootloop. It didn't even start the firmware. Any suggestions?
EDIT: We got into Fastboot. What are our options?
Right now your best option in my opinion is to flash Boot.img, recovery.img,cust.img and system.img that you will extract from the UPDATE.APP of your CURRENT Rom. Then just try the dload method again and again, it may not accept the firmware you try to flash but in this case just try another, but not a lower one because you need the rollback package to do that
Rayan19997 said:
Right now your best option is to pray for USB debugging to be enabled and then unlock the bootloader if you didn't do it earlier. After that you should try to flash TWRP
Click to expand...
Click to collapse
What should we do after we've flashed TWRP? When I tried flashing LineageOS 14 it decided to fail the installation somehow and be at an endless boot animation. So I'd like to get the phone restored to EMUI5.0.
Sorry, what I said was garbage, I just edited my comment, you're so quick lol
Rayan19997 said:
Sorry, what I said was garbage, I just edited my comment, you're so quick lol
Click to expand...
Click to collapse
Well currently there's a broken firmware on it of FRD-L09C432B943... Or something like that.
I think at this point he's looking at getting a new phone all together.
No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:
Rayan19997 said:
No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:
Click to expand...
Click to collapse
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?
Yeah on honor official site: Hihonor
Or with firmware finder
ZelafAry said:
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?
Click to expand...
Click to collapse
If you need a full firmware then you should visit official honor site..
If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot
hassanjavaid8181 said:
If you need a full firmware then you should visit official honor site..
Click to expand...
Click to collapse
I can't find any Honor 8 FRD-L09 downloads anywhere on the Huawei sites or Honor sites. They must've removed the downloads just like they did with the Honor 7..
Rayan19997 said:
If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot
Click to expand...
Click to collapse
I get that now and I know how to proceed in the future.
On another note, I got a good UPDATE.APP available but it refuses to install using the dload method because the versions are different. Does anyone know which partition the USERDATA.img file goes to?
You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8
Rayan19997 said:
You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8
Click to expand...
Click to collapse
Thank you for that link, I downloaded it and flashed it, I couldn't find it on any other hihonor site but this French one had it.
Again, thank you, it worked flawlessly installing and it updated instantly. You saved me from a lot of worrying and anxiety about breaking my friends phone lol.
I'm really glad to read that dude
thanks for the firmware been looking for it for very long!
btw you just saved another honor 8
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Chricap said:
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Click to expand...
Click to collapse
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Austinredstoner said:
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Click to expand...
Click to collapse
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Chricap said:
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Click to expand...
Click to collapse
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Austinredstoner said:
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Click to expand...
Click to collapse
Yes, I still have the TWRP installed, precisely version 3.4.0-0, since I could not find a working ROM I tried to debrand it (it was brand Tim) and I think I have done a damage to follow that guide, now I do not not even install the stock rom anymore. I don't know what to do at this point, I would leave the custom rom alone and reinstall its stock rom, at least debrand ...