Database Info

[Q] Huawei U8510 stuck at first boot - Bricked?

Help.
I completely screwed up but do not know where.
Had problems rooting but eventually made it with 'Automatic-Root-Enabler--U8510--v1.1' which worked first time.
Then used rom manager to install HuaweiU8510.zip which did not work so tried U8500_Huaweid.zip.
cache and Delvic cleared, rebooted and red huawei came on screen and there it stayed.
Removed battery, boot into recovery went into firmware update(image in dload but cant remember name) starts step 1 unpacking get yellow triangle with ! and says update failed. also tried again with zip files on sd card but back to red Huawei
Any one got any ideas please as I can get to the sd card but not to the internal memory and not adb/fastboot. So no way of getting a new recovery image into dload
Keith

Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...

Sarvesh50 said:
Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...
Click to expand...
Click to collapse
Thanks
1. no
2. trying once I get original rom
3. Funny it is every one I tried
Keith

I do own a galaxy s...
Once i had a similar problem...
It was caused by the filesystem
Samsung uses the rfs system but custom roms prefer ext4 which is better...
When your filesystem isn't compatible with your custom rom than you will have a startup problem so try to figure out if you have to change the filesystem.
can't post links from other sites cause i am a newby to xda forums this is really annoying
Check this
http://forum.xda-developers.com/archive/index.php/t-1200195.html

Restart loop

Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?

Well not having the phone in front of me, I don't really quite understand the issue myself - however, I would suggest using RSD Lite and one of the FXZ files to flash everything (including recovery) back to stock.
If you still have issues, there is a bigger problem (likely hardware failure).

Hello
sorry if my explanation was not clear.
I added a photo which shows the two steps in the operation of my phone.
Step 1: Start the phone .
Step 2 : boot ROM CM12
The Step 2 lasts 23 seconds then return to Step 1 and Step 2 and Step 1, Step 2 infinitely .
I hope this is understandable .
I read on the forum that used some RSD Lite but as I had not used for the ROM installation, I did not understand why use .
I'm a new user, i can't post picture, I send link by PM, thanks.

I thought my last post made it clear what purpose RSD Lite and the FXZ files are - they restore the phone to stock completely - ROM, recovery, everything will be reset to when it was stock from the factory (granted it may be a newer image than what shipped on the phone, but you get the point).
Again, as I stated previously, if you still have issues after flashing everything stock your issue is likely not software, but hardware.

I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.

Nicolas.636 said:
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Click to expand...
Click to collapse
The hardware issue is likely not related to the SIM modification. As to what exactly has failed, I'm not sure... perhaps the NAND or something else memory related.

Aouch aouch...
Thank you for your help.
I think it remains for me to search for a motherboard for photon Q.
Long life in the forum!

Use "borrowed" TWRP recovery image.
Nicolas.636 said:
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Click to expand...
Click to collapse
I had a similar incident a few days ago. I have a hard time stopping myself from pushing the limits. Usually I stop when it's broken. I tried RSD Lite, SDB sideload/ flash, zip install from recovery, fastboot(mine's dead), all with no luck.
Any how, If you have CWM, temporarily change to TWRP. If you already have TWRP it's easier.
XDA has a TWRP recovery image in the forum. Put that in your sdcard (I had to paste it from my computer because my xt897 was soft bricked). Flash from TWRP.
Worked fom me. got my phone back after 1 week of flashing everything and then some.
Good luck.
http://forum.xda-developers.com/showthread.php?t=2295643
http://forum.xda-developers.com/showthread.php?t=2295643&page=2

Hello
thank you for this new information.
I tried it and it worked with the ROM [PQ_ICS-Stock] but only with that one!
I tried the ROM [PQ_JB-421] , several Cyanogen ROM but still the same looping boot problem.
I tried several version of TRWP without success .
I do not understand why my Photon Q only works with this ROM [PQ_ICS-Stock] .
Is still a motherboard problem ?

Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?

Nicolas.636 said:
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Click to expand...
Click to collapse
If you can't RSD Lite, something is up. Either you are not doing the process correctly, or there is something wrong with the device (still).
Perhaps you were always on ICS and never made the official jump to JB? You say you can RSD Lite to an ICS version, just not a JB version? So 4.0.x works but 4.1.x does not?
Again I'm talking stock. If stock doesn't work, I wouldn't even attempt CM. Start with the basics, then work your way towards the aftermarket.

I agree that if the stock rom does not work after the installation with RSD Lite is that it remains something (software) .
The first motherboard I used 12.1 CM for several months it is that the phone supports android 5.1
I agree that it must abort running a stock ROM before flashing a ROM CM. But the ICS ROM STOCK works!
It is possible that I did not do the process correctly .
What surprises me is that the second board had the same problem with the ROM SPRINT !
I will do other tests.

Nicolas.636 said:
What surprises me is that the second board had the same problem with the ROM SPRINT !
Click to expand...
Click to collapse
This is the part that makes me think you are perhaps missing some step in the process somewhere.
Can you RSD Lite to ICS? Not flash it with TWRP. If that is successful, try to RSD Lite to the latest JB again.

I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.

Nicolas.636 said:
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Click to expand...
Click to collapse
Bad ESN shouldn't prevent booting... it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...

arrrghhh said:
it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
Click to expand...
Click to collapse
yes
I used RSD Lite 6.1.6 for flashing the ROM [ 2014-03-09 - TSv2 ] but the process has blocked after the flash.
Here is what I did :
1- run RSD Lite
2- Start the phone in FASTBOOT mode.
3- usb phone connection to PC
4- opening of the ROM [ 2014-03-09 - TSv2 ] and "uncompress and start flashing"
5- flash goes well
6- the phone reboots => Logo M red => telephone reboot => Logo M red => again ....
7- RSD Lite waits for the restart ... [ it waits again, LOL ]
8- I turned off the phone and I unplugged.
9- I turned on the phone who start properly, I arrived at the language selection screen .
The ROM is an android version 4.0.4 , I think you know this ROM .
Why the process with RSD Lite has blocked the phone to reboot ?
That's what I did wrong in the process?

I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.

Nicolas.636 said:
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Click to expand...
Click to collapse
Without having the device in my hands, it's hard to say for sure. The only difference I can see you are doing differently from me is using a newer version of RSD. I doubt that would be an issue, but may want to try other RSD versions.
In the end, I suppose if 4.0.4 works, use that...

Thank you for you help.
I'll buy a other PHOTON Q on EBAY.
I do other test with the new PHOTON Q.

Hello
I received my new q photon.
It is version 4.1.2
I unlocked the bootloader .
I made a backup with TWRP and OPEN_RECOVERY_209 .
I tried an installation of 3 different ROM but I have an error message !
I do not understand where does the problem ?!
Is this a bad version of TWRP or ROM ?

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

[Please help!] Unable to root Samsung S7 8.0

So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD

Devansh_Droidgeek! said:
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Click to expand...
Click to collapse
OEM unlocked???

cooltt said:
OEM unlocked???
Click to expand...
Click to collapse
through developer settings? yes

Devansh_Droidgeek! said:
through developer settings? yes
Click to expand...
Click to collapse
follow this guide here

Huawei P smart fig lx1 unlocked with potatoNV

Hey guys I finally got my phone working stable I guess I have to say it was a mission to even get it to run a custom rom in the first, keep in mind I am Not a developer but just a guy who loves to try new things as most of the curious minds out there anyways I was hoping to get the attention of someone that could help me now cause I can't seem to get this forsaken phone rooted now any insights on how I go about doing that will be much appreciated

the process i used to install the custom rom
And i say this with great seriousness do not format data using TWRP 4 or higher else you will get a bootloop.
ROM// Download Huawei P Smart 2018 from SourceForge.net currently using at the moment
TWRP// Download Huawei P Smart 2018 from SourceForge.net twrp 4 v1 by haky86
How to Install twrp 3.2.1 Root Huawei P Smart FIG-LX1 - twrp unofficial (unofficialtwrp.com) twrp 3.2
: theres a few i used but i guess its more of issue i had with it that i used more than one
first i flashed TWRP 3.2 using ADB and FASTBOOT to format phones data and factory resetting it again but it is highly recommended that if you do unlock your bootloader that you use EMUI recovery to factory reset before installing another custom recovery. the issues i had with TWRP3.2 is that after i installed the latest build of lineage OS
LineageOS Downloads
the operating system would not boot up however when i flashed stock EMUI 9 recovery Download Huawei P Smart 2018 from SourceForge.net i factory reset and it booted up as normal secondly i actually loaded TWRP 3.2 again because i saw the phone was booting up but the issues just came more anyways TWRP 3.2 couldn't read or id say display the information written to the phone as normal but to me it seemed everything was encrypted thus me installing TWRP 4 and that issue was fixed
there was few hours i couldn't get my phone past the Huawei part of the unlocked warning but that didnt stop me from trying to get it working again
I assume there will be a few people that has the twrp issue where it freezes again like i said do not use TWRP 4 or higher to delete the data i cannot stress this enough but you will end up having problems
so anyways i actually removed the nightly build from my phone cause i tried to installed MAGISK and couldn't get it working so i thought let me try and older OS build maybe theres some trick to get it rooted and boy was i wrong i cant figure it out maybe rooting is just not recommended for FIG LX1 i dont know but im 100% sure theres someone that can help me get it Rooted so currently I have this installed as OS Download Huawei P Smart 2018 from SourceForge.net
@HAKY86 my good sir i hope you get to read this and can help me if you can it would be much appreciated
anyways i hope we get to see more cool roms being made again for the P-smart FIG series