Related
Alright guys, so this happened 100% ON ACCIDENT but it actually worked! I wanted to let you guys know because maybe it will help some of the devs figure out how to eliminate the static boot for good.
I have the H910 ATT V20. I initially rooted it using Dirty Santa but, at the time, nobody had made a custom ROM for the ATT variant yet. I flashed the Konverged Kernel and from then on, I had the dreaded static screen on boot. @Tilde88 was extremely generous in offering to make a custom ROM if I provided some files for him and he made the first excellent NotSoStock ROM for the ATT V20. However, I had some issues installing it on the first try. When I tried to flash his ROM, TWRP gave me an error telling me I had a US996. I patched the zip with a file from Tilde88 and it worked like magic!
Since then, there has been a lot of progress in ROMs and kernels for all the variants. For the sake of experimentation, I have tried different ROMs and kernels to see how they affect the phone. Since my phone is registering as a US996, I flashed that variant of the NotSoStock ROM. The Werewolf Kernel from @USA-RedDragon is the only one I know of so far that does not have the static on boot. I have been flashing Werewolf and Konverged along with different ROMs to see the difference in performance and battery.
The ROM I am on right now is Extreme Syndicate from @elliwigy. Since it is based off of the stock deodexed US996 firmware, I thought it sounded great to try since it has NONE of the bloat from any of the various carriers. I read in a post by @AlkaliV2 here about flashing the stock kernel located on my computer from the original Dirty Santa root method:
https://forum.xda-developers.com/v2...-nrd90m-modded-notsostock-rom-t3525344/page21
That gave me an idea to download and flash the stock unlocked US996 kernel since Extreme Syndicate is based off of that. I had Konverged Kernel at the time. I flashed the US996 kernel, but forgot to flash SuperSU before boot... Woops lol. So I went back to TWRP and formatted my phone to start from a fresh flash, but realized I also deleted my ROM backup when I formatted my phone. So I decided to install a ROM and kernel fresh.
HERE IS HOW I FIXED THE STATIC BOOT
After formatting my phone, I flashed the Extreme Syndicate ROM with the Werewolf Kernel. I chose this kernel so there would not be any static on boot.
Then
I booted back to TWRP, made a backup just in case, and flashed my stock H910 ATT kernel from the file named bootbackup.img. After that, I flashed SuperSU, wiped Cache and Dalvik, rebooted... and BAM, just like that, no static! It says under software information that I am on kernel version 3.18.31. 3C Toolbox shows the kernel as Linux 3.18.31g12e8957
It is still fresh so I have to see how it goes with battery and performance. Initially, it was noticeably slower. I completely fixed this by:
1. Implementing all options under "One Click -> Performance Optimizations" in the app 3C Toolbox
2. Selecting "Performance" under Profiles in the app L Speed
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Yes, there is an updated driver branch using CAF sources that fixes static boot. I'm far too busy in life to get anything done, and before anything else, I have to get v6.0 for the H918 going. Once that is up (using the latest build and soruces from LG), I can move forward for 6.0 for the other devices.
nikktrikk said:
I just wanted to share this with everyone to put this info out there. I have not seen a fix for the static boot yet and though that this might be useful info for someone out there! I hope this helps!
Click to expand...
Click to collapse
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Hmmm interesting. Mine returned with:
Code:
3.18.31-g12e8957
[/QUOTE]
Do you have any idea why that might have happened? I used the file directly from the Dirty Santa folder, but maybe there is an issue since I flashed it over the previous kernel.
AlkaliV2 said:
This is an interesting approach, I'm not entirely sure why it would work but I'm willing to give it a shot. I'm not entirely convinced that you are running the stock AT&T kernel though since you are seeing performance loss and no static on boot. I don't have a normal method for ensuring that you have the stock kernel (like Wi-Fi calling being enabled) but I do have one way you could check. Use any terminal emulator (no root/su needed) and pass the command
Code:
uname -r
and let me know the output.
I have the stock AT&T kernel installed with everything working aside from static boot and mine reads:
Code:
3.18.31-perf-ge3230fb
Click to expand...
Click to collapse
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
nikktrikk said:
Also, I think it is an issue with my phone registering as a LG-US996. None of the ATT ROMs will flash onto it and I don't know how to convert it back to register as an H910. It seems like that is one of the primary reasons that the kernel I used from my computer may be having issues. Do you know how I can revert my phone? Nemisisg4 mentioned that when he tried to reflash the NotSoStockRom, it said no OS was installed. I also got that error numerous times when messing with different setups and it caused me to have to flash things all over again. I could not restore my saved backups of the 5.5 either after wiping the ROM I think because, since the ROM needed to go from the 5.1 to the 5.5, when I backed-up the 5.5, there was a conflict during the restore process.
Click to expand...
Click to collapse
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
AlkaliV2 said:
Alright, I was out for a little but I'm back now and I have a suggestion. I'm going to write up a short how-to but go here: https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
You are not going to follow that guide directly as I need to update it to include the actual stock kernel bootbackup.img but the backup files need to be placed in TWRP for the Restore function to work.
So to modify the steps a bit for your usage:
!) You need SuperSU 2.79 stable and your bootbackup.img file saved to your microSD card
1.) Put the files in the TWRP > Backups folder (preferably on your microSD card because we are formatting your entire data and internal storage) *
2.) You are going to go to advanced wipe and wipe everything except microSD and USB-OTG
3.) Go back and choose Format Data from the wipe screen and swipe to wipe data again just to be sure
4.) Reboot to recovery
5.) Now we want to restore the system image you have saved to your MicroSD card. Hit the restore menu, make sure the system checkbox is checked only, and slide to start
6.) Once finished head back to the main menu and choose Install > Install image and choose your bootbackup.img file
7.) Once done immediately flash SuperSU 2.79 stable
8.) Power off the device from the menu leave it be for about 30 seconds then turn it back on and let it boot.
It SHOULD work. Let me know if it doesn't and I wish you luck. Also, avoid US996 ROMs for the time being. I am getting the H910 image out to devs as quickly as I can and it has files that are pretty important to the hardware in our phone. If you get this to boot just use TiBu to remove things you don't want and always keep a copy of this backup ROM on your drive.
*If you do not have a microSD card to put these files on you can do a full wipe like I mention above, but you'll have to fully wipe it as I have instructed, reboot recovery to TWRP, hook the phone up to the PC at that point and copy the files you need over to it at that point.
Click to expand...
Click to collapse
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
nikktrikk said:
Wow, thank you for such a detailed post! So just to clarify, after flashing the bootbackup.img that includes the stock kernel AND the stock ROM? And this is basically unrooting my phone and putting it back to stock, so I would need to go through this process, then re-root?
Before you responded, I managed to flash the stock US996 kernel to my phone with the extreme syndicate ROM. So far it is lightning fast, the battery seems good. Usage so far is about 7 hours with an estimated time remaining of 35h 27 min. I know you said to avoid the US996 ROMs, do you think it is worth it to go back to stock if I am getting those stats as of right now, will the battery life and speed be comparable? Isn't the hardware the same, just each phone has it's own OS, hence why my phone functions on the US996 after the conversion happened? I have no idea about this so I am just throwing that out there to ask!
Thanks again for your help!
Click to expand...
Click to collapse
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
AlkaliV2 said:
I can't even begin to tell you what the right thing to do here is. I can only say what my experience was having my device run as a US996. Broken comfort view, no wifi-calling, FM radio not working (variant kernel related), and issues with battery drain. But that was my experience. If you are having good results running 996 then don't feel obligated to change. My post was just to get your phone back to being recognized as a H910. Now to answer your original question:
The files I linked to above in the guide are for the H910 system, recovery, and boot image made immediately after I got dirty cow working. The kernel in that backup set is the US996 kernel, not the one you need to go back to full rooted stock. The restore method I mention does not remove root or break TWRP it just puts back the stock ROM in full and then you flash bootbackup.img along with SuperSu to keep root and boot the stock kernel. It is the config I am running right now because it gets me all the features working aside from the static boot. So you only need to follow my guide if you can't get back to stock H910 rooted.
Edit: let me be clear in case it wasn't before. If you decide to use my backup files: do NOT use the boot or recovery image from those restore files. Use just the system restore image and your own personal bootbackup.img kernel along with SuperSu 2.79 stable.
Click to expand...
Click to collapse
Definitely makes sense. Yeah I have been having issues with battery drain and all that, as well. This is the very first time since I have been having issues with the US996/H910 conversion and incompatibility that I have actually got it to be stable. I also didn't like not having comfort view, and this actually fixed it! Comfort view now works on my phone, it didn't work earlier today before this most recent flash. I think that I will just give it some time before I make a decision and see how the battery fares. You have been a HUGE help, I really appreciate you taking the time to explain the process to restore my phone. I do want to do it, but being that it currently seems to be doing a lot better than before, I'll wait before making the leap back to stock just for comparison.
Help me
I also have h910 model but when i tried to boot after dirtysanta 3 rd step it didnt boot into twrp..even though i tried to flash recovery with fastboot flash recovery command.
I m stuck and static screen is a mess..plz help me
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
titmus said:
Hi, I'm a bit of a novice at this, can you please explain this line:
"flashed my stock H910 ATT kernel from the file named bootbackup.img"
Where do I get this file, and how do I flash it?
Click to expand...
Click to collapse
you where supposed to back up your original filesystem you would have gotten it from there.
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.
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader
z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore
Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.
Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise
P.S. restoring from nandroids brought me back to square 1..
z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over
Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.
So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
Code:
ROM Android version | 9
ROM Build ID | omni_guacamole-eng 16.1.0 PQ3B.190801.002 eng.mauron.20191115.213714 test-keys
ROM Version increment | 1907281556
ROM SDK version | 28
ROM/Recovery modversion | OmniROM-9-20191115-guacamole-HOMEMADE
Device Recovery | TWRP 3.3.1-72-26af64d9
Basically, the Omni junk is still on there somehow - even after the MSM flash, even after I upgraded to the latest Android Pie build before attempting all this. So I am fairly sure my partitions are messed up indeed. But how do I fix this? How can I re-create the factory / normal state?
Ps.: Attached the full log.
Stock factory reset? Twrp factory reset? I know you're thinking, if msm didn't work this won't. I am too. But you didn't mention and it sounds like it's worth a shot.
h8Aramex said:
So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
Code:
ROM Android version | 9
ROM Build ID | omni_guacamole-eng 16.1.0 PQ3B.190801.002 eng.mauron.20191115.213714 test-keys
ROM Version increment | 1907281556
ROM SDK version | 28
ROM/Recovery modversion | OmniROM-9-20191115-guacamole-HOMEMADE
Device Recovery | TWRP 3.3.1-72-26af64d9
Basically, the Omni junk is still on there somehow - even after the MSM flash, even after I upgraded to the latest Android Pie build before attempting all this. So I am fairly sure my partitions are messed up indeed. But how do I fix this? How can I re-create the factory / normal state?
Ps.: Attached the full log.
Click to expand...
Click to collapse
I use this tool to restore it to the original, you can test https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and use https://toolaio.tk/fastboot-roms/ Manage just let it run for about 5-10 minutes, everything is intact.
สุรินทร์ พลโธา said:
So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
I use this tool to restore it to the original, you can test https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and use https://toolaio.tk/fastboot-roms/ Manage just let it run for about 5-10 minutes, everything is intact.
Click to expand...
Click to collapse
It's all good then? Got everything working?
GeekMcLeod said:
It's all good then? Got everything working?
Click to expand...
Click to collapse
It works quite well as a pleasant machine.
GeekMcLeod said:
It's all good then? Got everything working?
Click to expand...
Click to collapse
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?
h8Aramex said:
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?
Click to expand...
Click to collapse
Why so salty? Also since msm resets your device to the factory stage, I'm pretty sure it's twrp that's messing things up. It's also funny how you said that you're not trying to attack the devs, then you blatantly attack them a few posts later. The devs are pretty much doing everything for free.
Edit: Just checked your logs and surprise surprise! You're using twrp 3.3.1-72, the one that was known to cause issues! Use .70 or .74, and how about you do some research before blatantly attacking the dev, Mr. "Senior Member".
Kaz205 said:
t's also funny how you said that you're not trying to attack the devs
Click to expand...
Click to collapse
I have nothing but respect to the real developers of XDA. Would help them in any way I just can and I am grateful for their work.
However, check the OP in Omni 10's thread. I'd call that person anything, but a "developer". That person does not belong to this crowd in my book.
Anyhow, let's get back to the main topic. I managed to fix everything up and recovered the phone.
Once I upload everything to a mirror I'll update the thread with info.
Thanks for the twrp tip by the way.
The best way I find is use a fastboot rom with flash all. I like to boot to twrp first format data then boot back to bootloader and the use the flash all file inside whatever fastboot rom I decide to use
h8Aramex said:
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?
Click to expand...
Click to collapse
Which Gapps package are you trying to flash? Because the Google apps packages are not supported in any way by LineageOS.
https://wiki.lineageos.org/gapps.html
Also if you go into twrp and then in the advanced wipe menu, there is provisions to resize your file system. I have had to use that in the past in order to be able to flash gapps, exactly as you described. Just swipe to resize the partition. Should fix your problem (provided you are installing the correct gapps in the first place).
So this morning I went to check on lineage OS news oh, and I found out that they released today for all pixels. I am running it with no issues although I would recommend to download the micro gapps package cuz if you do the Nano or anything below it will give you issues with your phone reading SIM card. Aside from that I had successfully running the rom with magisk installed.
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
i42o said:
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
i42o said:
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
Click to expand...
Click to collapse
Is 90hz working??
ahoslc said:
Is 90hz working??
Click to expand...
Click to collapse
Read just one or two more posts above the one you quoted to find your answer.
bradical711 said:
Read just one or two more posts above the one you quoted to find your answer.
Click to expand...
Click to collapse
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
i42o said:
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
90hz works, 70% plus brightness on coral gives 90hz, below is 60hz. flame has some different tunings percentage wise, but same concept.
RefreshRate will work as soon as we have an official R image I can steal a single APK from.
We won't be implementing Squeeze or Soli most likely - it's RE, and given scrutiy over large projects and reverse engineered code, we likely won't see it unless it's reimplemented OSS (DU reverse-engineered it, but didn't clean room re-implement).
ahoslc said:
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
Click to expand...
Click to collapse
It works.
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Madjax2020 said:
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Click to expand...
Click to collapse
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
i42o said:
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
Click to expand...
Click to collapse
thank you sir for the reply. However i could not get it to be stable. The initial setup failed no matter what i tried. The error of data tansfer tool would fail. I want to run this as it seemed very smooth, however i think i need to wait for another update or something. i followed the OP to the t and nothing seemed to work properly for me.
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
I'll try again thanks for the info
Seems the wiki says you can sideload gapps right after sideloading the OS, the OP said doing that causes issues lol. But he'll I'll try it anyway
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
Got this running great, with gapps. Was wondering if you're getting the issue I am with google assistant. It seems to freeze up and not be usable.
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Madjax2020 said:
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Click to expand...
Click to collapse
You do remember I said micro right? I specifically explained that by using nano you would have no cell phone connectivity and upon transfer tool just put no transfer
XMayhem2099 said:
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Click to expand...
Click to collapse
Yes it is still there but much less now
Face unlock working?