Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs
Related
So for various reasons, many problems with cm13, candy and lineage ROMs, I decided to go back to cm12 (carbon ROM)
Wasn't simple but eventually I got there and everything was good for a week. Then for some reason the wifi stopped working, getting stuck at 'turning on wifi'.
At this point I couldn't do much of anything except restore my old backup of carbon ROM.. couldn't install cm13 (hang at first boot) couldn't install candy 6 or 7 (boot loops) or lineage (boot loops). Couldn't even restore backups I'd made of those others.
So, several hours of effort got me back to rooted stock 5.1. Everything works right now, including wifi, but I'm stuck at stock which of course is less than ideal. I figured I could try a clean install of carbon ROM but this is now my problem. When I try to install via TWRP, I get an error saying that it requires bootloader .....b322 but my bootloader is 'unknown'.
A week of fiddling and flashing and I'm stumped. Anyone know what's wrong and how to fix it?
Sent from my MT2L03 using XDA-Developers Legacy app
Hello guys,
as the title says I am currently with the mobile data connection not being established on custom ROMs, the official MIUI ROM works fine. Before trying to go to LineageOS 14.1 I ran this 13.1 ROM for quite some time successfully.
This is what I did since trying to migrate to Andoid 7.1:
I flashed the latest MIUI Global Dev ROM, this locked my bootloader again, so I tried this for installing TWRP and custom ROMs with locked bootloader and this for unlocking the bootloader unofficially. Both methods generally worked, but mobile data did work on neither of them (I checked for the correct APN).
So I tried to go back to the LineageOS 13 ROM (clean flash, since I accidentally deleted my backup) I used before, but it also does not work on that version anymore.
Does anyone have any idea what the issue could be or how I could possibly find out what causes this?
Edit: I am now actually back to the latest MIUI Global Dev and hoping that I am able to unlock the bootloader officially eventually. But any tips on the issue above would still be appreciated.
Edit 2: On the 8.0 NitrogenOS mobile data does work. I first thought that it yet had to be an APN problem, so I copied the settings from this ROM to the LineageOS 14.1 ROM and deleted all other APNs, but that actually did nothing, it still did not work. So I guess I will stay on 8.0 for now, although I wanted 7.1 because of XPosed.
Edit 3: Suddenly stopped working on Android 8. Seems to work on the first boot after flashing a Android 8 ROM and then not anymore. Going back to MIUI...
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
triplec0re said:
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
Click to expand...
Click to collapse
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
b0mb said:
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
Click to expand...
Click to collapse
I did just recently find a persistent method. Read here: https://forum.xda-developers.com/showpost.php?p=70887635&postcount=9
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
try twrp 3.3.1 unofficial from
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
also then flash vendor image https://mirror.akhilnarang.me/MIUI/beryllium/ (9.6.27 is the popular)
flash LINAGE OS
flash DFE Treble https://drive.google.com/file/d/1As6z5v7NEIfOk67jXHBX34cbnFZdEjy9/view ,
later install magisk 19.4
now try one by one all three version of Twisted kernels ( the developer maintains 3 versions based on touch drivers (nvt)
https://forum.xda-developers.com/poco-f1/development/kernel-twisted-kernel-v4-0-beryllium-t3902838
i am hopful you will fix it
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
Worked for me! Thanks!
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
I had an experience as bad as yours. After flashing the last miui.eu, I went to boot and the phone does not leave the boot right away. I tried to enter TWRP and the touch just didn't work. I ended up flashing the official TWRP, also none of the touch works. I started getting desperate and settling for formatting for ROM stock and losing my 2 year old data, because I went to fastboot and flashed stock 11.0.8.0 and guess what? the touch didn't work, even in stock, I started to go crazy. So I had the stupid idea of putting the stock and blocking the bootloader, I ended up ****ting even more because even after the flash and blocking the bootloader the touch was dead. I was already giving up and thinking about paying someone as access to EDL mode to restore the phone. I ended up seeing your post and had the idea of plugging a mouse into the cell phone's type c input, and believe me the mouse cursor worked. Then I managed to unlock the bootloader again and flashed the stock that you recommended, and voiala the touch went back to work. I ended up going back to miui.eu and I'm ready for new flashes. It seems that we like to suffer LoL. I think this topic should be fixed at the top in case anyone else falls into this insane problem.
Reflash firmware n try ones.. only firmware
dorfohm2 said:
Worked for me! Thanks!
Click to expand...
Click to collapse
Im having the same issue.What should I do??My touch was working totally well before flashing TWRP.
solved by plugging in a mous in TWRP and navigating the UI to restore my "full" backup of all partitions! if you have done a backup! cheers and thanks for the idea of the mous! not expected it to work in TWRP though!!!
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine