Related
Stock M8 GPE 5.1 LMY47O.H9 ported for the Verizon variant of the M8
Modifications made to this ROM are for Verizon network stability, stock boot.img device tree binary was modified to work on CDMA devices, init.d support, selinux permissive and you should not receive any official OTA notifications.
Its recommended to be on the latest Verizon firmware 4.17.605.9
Install: TWRP is recommended
1. Reboot to recovery
2. Wipe/Factory reset if coming from another ROM
3. Flash ROM
4. Reboot
5. Enjoy, First boot will take 5 to 10 minutes
Special notes:
1. If you were using the partition f2fs, you must switch back to ext4 first.
2. Insert Sim when going through the setup wizard. Just hit skip and continue on with the setup.
3. Unknown phone number will show in settings under Sim Status. You can still make and receive calls and your number automatically populates after first reboot.
4. If you have issues with 3g/LTE data hand off, please call Verizon and have them reset/refresh your SIM or signal whatever they do. Maybe even get a new SIM card.
DOWNLOAD:
AFH: https://www.androidfilehost.com/?w=files&flid=39415
Google Drive: https://drive.google.com/open?id=0B_2pYqG5OJVYMkx0bXB4UTRyd00
DevDB: http://forum.xda-developers.com/devdb/project/dl/?id=14457
MD5: d51a76b9c3e0c94e89d48054f4b91a6e
XDA:DevDB Information
Verizon M8 Stock GPE Rom, ROM for the Verizon HTC One (M8)
Contributors
undarated, enewman17
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.17.605.9
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2015-09-17
Created 2015-09-18
Last Updated 2015-09-27
Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.
This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.
dragontology said:
Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.
Click to expand...
Click to collapse
I haven't had any issues with gps dropping out all all. I travel a lot for my job and have been running the same version as posted for the past 5 days straight.
Check out and let me know if you have any issues
Robby_Rimal said:
This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.
Click to expand...
Click to collapse
I'm not sure what went wrong. The rom does boot on the Verizon M8. If you check out the screenshots, those are screenshots taken from my phone. The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs. Maybe bad download?!?!? I'm not sure but the rom does boot and run. It does take a while for the rom to boot. It's too early to tell whats going on just yet.
Bootloops on VZW
grislieber said:
Bootloops on VZW
Click to expand...
Click to collapse
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.
undarated said:
The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs.
Click to expand...
Click to collapse
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.
whaevr said:
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.
Click to expand...
Click to collapse
undarated said:
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.
Click to expand...
Click to collapse
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.
mattyd3 said:
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.
Click to expand...
Click to collapse
I didn't supercid myself. I changed everything in the build.prop to match Verizon by removing any other cid and replacing it with our own. I haven't done anything special to get this to boot on my end. I have the usual set of characters. S-off unlocked, bootloader, latest firmware, latest TWRP, and root. Nothing else special at all.
This rom has no mods or anything else that would make it prone to any issues as far as booting up and running on our M8's. It's the same rom the Google put out except with everything needed for Verizon.
There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!
Div033 said:
There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!
Click to expand...
Click to collapse
I'm using his 5.1 firmware also. I was running his rom prior to porting this over with no issues
Just to clarify, bootloops and endless boot are very different animals. A boot loop loads the Android OS and then reboots automatically, usually instantly. (I once had a bootloop, on another device, that gave me about a minute.) Endless boot means it just doesn't boot. If this is anything like DH's GPE, first boot will take 8 minutes and change. Maybe less as it has fewer apps to optimise for. Legit 20 minutes is endless boot. I'd say to give up after 12-15.
I wonder if maybe using another kernel might work? I don't know what all needs to be changed to get an international ROM to work on an American phone, but I'd guess the kernel would be one of them.
Just speculating as I haven't tried it yet.
Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...
Is there any way to get Hotspot working? I have unlimited and need it.
Thanks
Robby_Rimal said:
Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...
Click to expand...
Click to collapse
I honestly have no idea why the rom isn't booting for you guys other than whats been mentioned. The kernel is the exact same one that came in the original rom. I didn't change it either. Honestly, when testing the rom before porting it, all I did was make the changes in the build.prop for Verizon. It's actually a straight forward port. It was a lot easier than it was coming for older JTC devices that i ported roms for.
cuban11182 said:
Is there any way to get Hotspot working? I have unlimited and need it.
Thanks
Click to expand...
Click to collapse
Hotspot is already unlocked by default. It is under Settings, More and Tethering & portable hotspot.
Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!
undarated said:
Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!
Click to expand...
Click to collapse
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?
cntryby429 said:
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?
Click to expand...
Click to collapse
Whew, Glad you got it to work brother. Duo camera? Im not sure. there is a camera app. It's the stock google camera. Should be on the bottom right of the launcher. I'll check on duo camera.
UPDATE: Just took a picture and went to edit it. it had the option of HTC photo edit and photos. I picked HTC photo edit and it had the options for UFocus and Dimension Plus under effects. Hope thats what your looking for.
Alright, sorry I just got back. Yes, the Rom booted perfectly. It is running buttery smooth!!! Sorry man...
I never get good downloads with MEGA. It always looks better but does something weird.
Downloaded the second time with Google Drive. This time the Rom flashed.
Hey undarated, don't worry man. This thing works perfectly!
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5
I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.
When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately
OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314
Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.
Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate
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.
Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?
Is it possible to get a custom rom without deleting all my data?
OR is it possible to add multiple roms and choose which to boot to to try them?
Currently rooted on OnePlus 7 pro magisk international firmware oos
I'd suggest the safest thing to do since you're rooted is to perform a TWRP backup, then try out all the different ROMs. That way you always have the option of reverting back.
I haven't heard of being able to boot from multiple ROMs, sounds pretty neat though.
klym.software said:
I'd suggest the safest thing to do since you're rooted is to perform a TWRP backup, then try out all the different ROMs. That way you always have the option of reverting back.
I haven't heard of being able to boot from multiple ROMs, sounds pretty neat though.
Click to expand...
Click to collapse
I was thinking something like dual boot on desktops
No, unfortunately dual boot for smart phones hasn't been available for sometime.