Rom doesn't boot - General Questions and Answers

Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?

Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021​
IMO you should contact developers of Bliss OS to get your issue fixed.

Recovering Spaghetti said:
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Click to expand...
Click to collapse
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!

jwoegerbauer said:
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021​View attachment 5799499
IMO you should contact developers of Bliss OS to get your issue fixed.
Click to expand...
Click to collapse
Hi,
The thing is I also tried DotOS & OctaviOS & the issue perseveres

vdun1188 said:
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
Click to expand...
Click to collapse
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.

Recovering Spaghetti said:
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Click to expand...
Click to collapse
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.

Recovering Spaghetti said:
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Click to expand...
Click to collapse
Understood. For some reason that is beyond my comprehension, it seems it is sometimes suggested to install stock and then a different custom ROM. Again, I don't know what it is actually supposed to do, as I've stayed with LineageOS to keep it simple. I'm not saying to stay with stock, just use it to get phone back to default, then start from there.
nuclear option..stock - hahaha )

Gawd Damit, I tried LineageOS too & a bunch of other stuff & it's always the same problem. I'm all out of ideas now.

Please help, Tried every ROM, same result, doesn't boot
Hi, I've got a Samsung Galaxy A10 SM-A105F and I tried installing all kinds of different roms on it and they install just fine but then when i go to boot to system I end up in this hell hole of perpetual booting and restarting. I've been at it...
forum.xda-developers.com

Related

[Completed] Gt-N5110 root problem

Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor

Problems installing lineage 14.1 on Galaxy Note 10.1 GT-N8010

Tried lineage-14.1-20170305-UNOFFICIAL-n8013.zip on a Galaxy Note 10.1 GT-N8010 (16GB), but after reboot, i am stuck in a never ending "boot logo" (?) (blue circle repeatedly shifting from right to left on a blue bow, nothing else), tried it twice, waited twice for more than 15mins, nothing changed (nevertheless, I could successfully install cm-13.0-20160831-UNOFFICIAL-n8013.zip).
Has anybody sucessfully installed 14.1 on a GT-N8010 ?
Further info: I have an additional 64GB-SD-card where I stored the aforementioned lineage file as well as open_gapps-arm-7.1-nano-20170418.zip and open_gapps-arm-7.1-stock-20170418.zip.
Tried all installations (also cm-13) using twrp-2.8.6.0-gt-n8010.
Any comments appreciated, even more so if they help getting 14.1 installed.
Regards
aqua14
2017-04-19 10:30 (MESZ)
Additional observation while again trying to install lineage-14.1-20170305-UNOFFICIAL-n8013.zip:
* Meanwhile I found that lirokoa recomended the TWRP version mentioned in the CM13 thread, i.e. twrp-2.8.7.0-gt-n8013 (instead of 2.8.6.0 in my first try) and managed to install it on my Galaxy GT-N8010, but after all, this made no difference.
* However, while carefully watching the flash log I found that the "target" was logged to be "samsung/p4noterfxx/p4noterf: 4.4.2/....", and not "samsung/p4notewifi...." as I rather would expect for a GT-N8010.
Hence my question: can it be that (a) either during the paketing of lineage-14.1-20170305-UNOFFICIAL-n8013 something went wrong, or that (b) my tablet pretends to be a different one (namely GT-N8000)? I suspect this confusion could be the reason of the aforementioned boot trouble.
At least I am sure of this fact: I haven't got a tablet with phone function, its the version only having the wifi function, and in the system info provided by JellyBean as well as KitKat I could read its the GT-N8010.
Any constructive hints or suggestions appreciated
Regards
aqua14
Additional observation:
* Both lineage-14.1-20170305-UNOFFICIAL-n8013.zip and lineage-14.1-20170116-UNOFFICIAL-n8013.zip don't work on my GT-N8010 (reboot after flashing leads to a boot loop) , whereas cm-14.1-20161208-UNOFFICIAL-n8013.zip did work (not everything tested yet, but wifi, installing apps (another keyboard, file manager, ...) worked ok.
2017-04-20
Eventually ...
I guessed just from the beginning, that the right path might again be hidden in all the tidbits given in the discussion around the lineage 14.1 thread (hxxps://forum.xda-developers.com/galaxy-note-10-1/development/rom-nougat-t3505239)
... and indeed! It took me a while to crawl through all comments, questions, answers, and unfortunately also complaints, the latter in some parts being expressed even in close-to-nasty manners. Being a developer as well (DB area) I as well appreciate constructive criticism and prefer it to demotivating complaint. However, some of the participants obviously never have learnt making an effort to keep the difference between both, maybe they are even unlucky enough not to perceive hours and hours of voluntary work of their contemporaries as a gift. Hey guys! Behave!
Whatsoever. I finally made the way through the texts and even managed to install the latest version (lineage-14.1-20170305-UNOFFICIAL-n8013.zip) and ... beneath my sincere thanks going to lirokoa (taking a bow 4 u), I'd like to greet and thank all the testers *and* contributors of helpful hints (regarding the installation of the ROM itself as well a manifold of aspects to special apps), also including especially those who took their time to precisely & factually describe which procedure did fail (!), which -in sum- made my day start successfully now!
For all those still struggling: keep trying!
After all this reading I restarted a new try and had my breakthough ~after having read the following comments in the aforementioned thread: #352/p.36, #364+#365/p.37 and some others of similar content, hence thanks also to alessandro_xda, hektor2hektor2, CDiazF04, but also all the others who keep the discussion vivid and interesting, and a special smile to miz_pimp for having increased the level of friendliness throughout the course .
And yes, I agree that many contributors are right in suggesting to include the one or other hint to the post #2 of liroka.
I guess it's presumably just lack of time on his side that this has not yet happened. On the other hand... :-> if I could walk through all the interesing discussion in one evening and draw my conclusions in order to get a free ride to another "new life" of my ol' N8010, ... I am quite positive that others can do so as well.
Continuously following the discussion...
aqua14
Thanks guys!
Just had the same problem. I just needed to upgrade twrp and try again. I really appreciate this site! Now my old tablet is doing better than my husband's new one.
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
macgd016 said:
Finally loaded Lineage 14.1
I have just updated my GT-N8010 with lineage-14.1-20170810-UNOFFICIAL-n8013.zip + open_gapps-arm-7.1-mini-20181010.zip & used the latest TWERP release 3.0.2 to do this.
I initially tried loading these two as above, the first issue was that having loaded them the tablet would get stuck with a battery symbol and would not boot. The way I found around this was to boot the tablet into Odin mode but choose Reboot Phone rather than going into Odin itself. This then enabled Lineage to boot but it then got stuck in a loop, the lineage logo would go through its line with a moving O, then have three O's and start again.
Eventually I found that I could get cm-13.0-20160831-UNOFFICIAL-n8013.zip to load with open_gapps-arm-7.1-mini-20181010.zip and this worked well. I then did a dirty load (No Wiping) of lineage-14.1-20170810-UNOFFICIAL-n8013.zip and this is now working without problems.
Hope this helps and best of luck!!
Click to expand...
Click to collapse
Have you tried out my LineageOS 14.1 ROM? https://androidfilehost.com/?fid=1322778262904016892
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
macgd016 said:
I'm sorry to say that I have not as I was not aware of your rom till now so thanks for for your post and I have downloaded it just in case I find issues with 14.1-20170810. Out of interest how does it differ from 14.1-20170810
Click to expand...
Click to collapse
Mine is more up-to-date. But I will be making a update for that ROM later this week.
Here is my thread for the ROM: https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514
Oreo rom for Samsung galaxy note 10.1 gt n8000
Pls any Oreo rom for gt n8000 my nougat rom can't play videos since i rooted it, after unrooting it still can't play any video. Pls is there any fix.
Flash stock rom via Odin.
JJEgan said:
Flash stock rom via Odin.
Click to expand...
Click to collapse
Will flashing the phone with lineage 14.1 again help? Cus I can't go back using stock rom
Back to stock then flash custom rom.
Problems fixes use SEARCH.
Rom is in testing so its up to you to flash with potential problems or not .
I have the same problem. Note 10.1 N8010 and it is stuck on the logo " blue circle repeatedly shifting from right to left on a blue bow".
I cannot locate the file TWRP for the note 10.1 N8010.
The suggestions were to update Twrp but the file I have found online is (
twrp-3.4.0-0-lt03wifiue.img.tar7.5M2020-06-23 21:11:34 EDT
This file is loaded using odin and it is successful but the Twrp doesn't work anymore. Therefore, I had to go back and load the file (twrp-2.8.6.0-gt-n8010.tar).
Can someone please help me with this issue.
TWRP site is twrp.me
Có ai up rom android 7.1.2 hoặc 9.1 cho galaxy GT-N8010, qua TeamViewer không? cảm ơn.
[email protected]
Translated by GT:
Has anyone uploaded rom android 7.1.2 or 9.1 for galaxy GT-N8010, via TeamViewer? thank.
[email protected]
See your other post

Cyanogen mod ROM repository

Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
duratto said:
Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
Click to expand...
Click to collapse
Firstly,this should be in QnA..
Secondly,
For latest recovery,
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
Recommended rom- https://forum.xda-developers.com/on...m-kernel-unofficial-lineageos-14-1-3-t3626403
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
duratto said:
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
Click to expand...
Click to collapse
Yes,to flash recovery the process is same as you did for the previous Twrp that is now on your device.

Samsung Galaxy S Relay most current CM ROM and TWRP?

Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.

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.

Categories

Resources