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.
Related
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
CyanogenMod 13.0 : Download
Changelog : Changelog
Open GApps : Download ( arm, 6.0, nano )
TWRP : Download​
CM13 Nightlies, ROM for the Sprint Galaxy S5
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly, now moved to 14.1
UPDATE 6/14: Looks like there's an issue that 5ghz network doesn't work on higher bands, but it works on 36-48 and bluetooth. Hopefully it will be fixed soon.
UPDATE 6/23: There's a fix attempt on boot image. Link. Thanks to @haggertk
UPDATE 6/27: Looks like Bluetooth and Wifi issue have been fixed since 6/25 nightly.
Thanks to @haggertk
Created 2016-05-12
Last Updated 2016-11-29
Reserved
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
alexclang said:
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
Click to expand...
Click to collapse
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
e-j said:
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
Click to expand...
Click to collapse
Excellent!! I'll just install the latest nightly for CM13 just like I was going for 12.1 and hopefully things will go smoothly!
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
UPDATE/PSA: USE THE NANO GAPPS AS STATED IN THE OP. NANOGAPPS INFINITY OPENS THE DOOR.
e-j said:
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
Click to expand...
Click to collapse
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
alexclang said:
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
Click to expand...
Click to collapse
Got it working after I realized the OP specifically mentioned the "nano" GApps variant; booted fine after a clean install of CM13 & the nano zip.
Issues w. CM13 flash
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
lentm said:
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
Click to expand...
Click to collapse
Yeah that was exactly the issue. Reflashed 5.0 then made the jump and it worked perfectly. So much wasted time...
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
e-j said:
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
Click to expand...
Click to collapse
Yeah reflashing lollipop then installing cm13 did the trick.
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
has anyone got themes to work ine keeps crashing
manolze said:
has anyone got themes to work ine keeps crashing
Click to expand...
Click to collapse
Mine works fine with Puzzled UI - CM Theme from Play Store on 5/20 build.
I have no working theme chooser on this releaese
xenokc said:
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
Click to expand...
Click to collapse
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
xpm69420 said:
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
Click to expand...
Click to collapse
Theme chooser works great for me, not having any issues with it. I am having an issue with the time being or of sync when set to automatic... How'd you fix it? Also, what's wrong with the dialer... can't say I'm having any issues there either.
unclejuju said:
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
I little late here, but CM 13.0 did NOT fix the S5 bluetooth issues. Still have the skipping and studdering.
Im having some trouble with my OPX. I was running CM13 nightly of sept 20th. Today i wanted to update my OPX to the latest nightly, and make a fresh start, so i took some backups of apps, downloaded the latest nightly (not OTA), went into TWRP, did a full wipe, and flashed the 10/15 nightly and opengapps pico package.... Thats when the fun began.
All my phone shows is the Oneplus X logo. (without powered by android). I am able to turn it off, and reboot into recovery, and flash another zip, but so far ive tried flashing 6 different CM13 nightlies, and all give the same result.
I was a pokemon player with root and xposed, so my guess was that systemless xposed, magisk and superSU were causing trouble. So ive tried running all the uninstaller packages, to no avail.
i CAN run a nandroid restore from 1 week ago. i can boot to that nightly version. it works.... but as soon as i try to update it again, or even wipe all data, it doesnt want to boot anymore. i thought that as long as i had TWRP things should be easy to fix, but im running out of ideas. Uninstalling xposed, magisk and superSU in this backup, and rebooting, still works, but the same problem arises after updating.
Im pretty sure the answer is simple as hell, but i must be overlooking something. any sugestions?
I just found out you need a new bootloader... should have looked harder before starting this thread (was searching for over an hour, but in the wrong places). I'll try the guide in the CM thread.
same exact thing happened to me, wasn't aware you needed new bootloader, think you could share the link?
rx15901 said:
same exact thing happened to me, wasn't aware you needed new bootloader, think you could share the link?
Click to expand...
Click to collapse
Here.you should always keep an eye on general section,thats where all the guides are,also should read the thread before flashing a rom.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
Luckily I'm using now my S5 Galaxy (G900F) with lineage 16.0 cause my LG G5 (H850) is driving me crazy.
What I did so far:
+Bootloader unlock
+Installed TWRP 3.2.3-2 than an update to 3.4.0
+flashed no-verity-opt-encrypt-6.1
+wipe format data and advanced wipe with cache + system
+flashed latest official lineage-17.1-20200705-nightly-h850-signed
The big problem is when I try to shutdown my smartphone its vibrating wild and instead of doing the shutdown its lunching a reboot. Only way to completly shut it down is to remove the battery. Did I miss anything?
Official instructions are not very usefull cause the sideload method didn't work either. I thought because its classified as official that 17.1 is running stable on H850 If I knew that before I would buy a different smartphone cause Samsung was way more custom rom friendly (had no issues with my S3 LTE and now with my S5). Since 2 weekends I try to fix this issue and read xda postings + user feedback on reddit but sadly haven't found any solution till now.
S5vsG5 said:
Luckily I'm using now my S5 Galaxy (G900F) with lineage 16.0 cause my LG G5 (H850) is driving me crazy.
What I did so far:
+Bootloader unlock
+Installed TWRP 3.2.3-2 than an update to 3.4.0
+flashed no-verity-opt-encrypt-6.1
+wipe format data and advanced wipe with cache + system
+flashed latest official lineage-17.1-20200705-nightly-h850-signed
The big problem is when I try to shutdown my smartphone its vibrating wild and instead of doing the shutdown its lunching a reboot. Only way to completly shut it down is to remove the battery. Did I miss anything?
Official instructions are not very usefull cause the sideload method didn't work either. I thought because its classified as official that 17.1 is running stable on H850 If I knew that before I would buy a different smartphone cause Samsung was way more custom rom friendly (had no issues with my S3 LTE and now with my S5). Since 2 weekends I try to fix this issue and read xda postings + user feedback on reddit but sadly haven't found any solution till now.
Click to expand...
Click to collapse
Any update?
If coming from stock rom I think you need to format data during the wipe process. Also, I recall reading in order to get 17 working you may need to be coming from Lineage 15 or 16, although I wouldn't swear to it (not currently on lineage). Did you flash no-verity last? Even though you seem to dislike it, I'd recommend troubleshooting within the Lineage 17.1 post.
https://forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807
good luck!
Aimless Rambler said:
Any update?
If coming from stock rom I think you need to format data during the wipe process. Also, I recall reading in order to get 17 working you may need to be coming from Lineage 15 or 16, although I wouldn't swear to it (not currently on lineage). Did you flash no-verity last? Even though you seem to dislike it, I'd recommend troubleshooting within the Lineage 17.1 post.
https://forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807
good luck!
Click to expand...
Click to collapse
Thanks for trying to help me out. Sadly I hadn't any luck yet - I will test my micro sd card cause I've read in a different posting that damaged micro sd cards can also cause bootloops.
The whole process to install 17.1 from stock rom seems not very well documented - this is the biggest issue I'm facing at the moment actual it's more like a try and error thing which realy sucks. Do you know if these bootloops are maybe logged in a file somewhere? I guess in this forum are enough tech people who can deal with such log files and can tell me whats going wrong.
I can't post my problems somewhere else (restricted to Q&A part of the forum) cause I'm a newcomer so forum system is giving me some restrictions.
S5vsG5 said:
Thanks for trying to help me out. Sadly I hadn't any luck yet - I will test my micro sd card cause I've read in a different posting that damaged micro sd cards can also cause bootloops.
The whole process to install 17.1 from stock rom seems not very well documented - this is the biggest issue I'm facing at the moment actual it's more like a try and error thing which realy sucks. Do you know if these bootloops are maybe logged in a file somewhere? I guess in this forum are enough tech people who can deal with such log files and can tell me whats going wrong.
I can't post my problems somewhere else (restricted to Q&A part of the forum) cause I'm a newcomer so forum system is giving me some restrictions.
Click to expand...
Click to collapse
I had bootloop problem with lineage-17.1-20200712-nightly-h850-signed.zip on my H850 although no problems with the previous build (20200705 ) installing today.
Following : wiki.lineageos.org/devices/h850/install/ was clear and straight forward for me.
- unlock bootloader
- install TWRP
- sideload Lineage + open Google apps
cheers
dpir said:
I had bootloop problem with lineage-17.1-20200712-nightly-h850-signed.zip on my H850 although no problems with the previous build (20200705 ) installing today.
Following : wiki.lineageos.org/devices/h850/install/ was clear and straight forward for me.
- unlock bootloader
- install TWRP
- sideload Lineage + open Google apps
cheers
Click to expand...
Click to collapse
I bought a fresh LG data cable and setup a complete fresh Linux Mint installation on my notebook. In TWRP I followed your tutorial (wiki.lineageos.org/devices/h850) and did fullwipe followed the tutorial here to install adb tools on Linux and was able to sideload "lineage-17.1-20200719-nightly-h850-signed.zip". Sideload succeeded (confirmed on linux terminal and TWRP). After sideload I did reboot and I got configuration menu from lineage. After skipping most of the config steps I did reboot and AGAIN BOOOOOOTLOOOOOP no complete shutdown.
can be closed solution was first flashing Android 8 stock rom with uppercut (H85030f_00_OPEN_EU_OP_1122.kdz) than flashing custom rom based on Android 9 (lineage-16.0-20200811-X86CPU-h850 - thank you to the author) and than I was able to flash official lineage 17.1 than bootloop was suddenly fixed. Each time after flashing I just did normal wipe (confirming with yes).
official tutorial completly sucks:
https://wiki.lineageos.org/devices/h850/install
-> sideload is not necessary and when you come from older Android Version you have to flash Lineage 16 before (no evidence and no image in download section).
So I really messed up I think.
My friend - who is on vacation had borrowed my phone earlier this year, and for some reason didn't reset it properly.
Now I need it again, but I couldn't start it up, due to the phone being locked to his Gmail account.
So I went into TWRP and reset the phone, did a wipe on Dalvik/Art Cache, System, Data and Cache. Then I realized I just deleted the ROM that was previously on it, so I downloaded another ROM for the phone. But it wouldn't finish booting after starting to load the system, so I downloaded another one. This one still won't boot up after coming to the system bootup after the LG V30 Thinq logo has shown. I have tried Havoc and Liquid ROM with and without gapps.
My phone is the Korean version.
Do I need to flash some kind of Magisk or SuperSU with the ROM, or can anyone help me so I can get my phone working again?
BobberK said:
So I went into TWRP and reset the phone, did a wipe on Dalvik/Art Cache, System, Data and Cache. Then I realized I just deleted the ROM that was previously on it, so I downloaded another ROM for the phone. But it wouldn't finish booting after starting to load the system, so I downloaded another one. This one still won't boot up after coming to the system bootup after the LG V30 Thinq logo has shown. I have tried Havoc and Liquid ROM with and without gapps.
My phone is the Korean version.
Do I need to flash some kind of Magisk or SuperSU with the ROM, or can anyone help me so I can get my phone working again?
Click to expand...
Click to collapse
What was the previous ROM? If it was LOS-16 based, you can't replace with LOS-17 based ROM without first flashing stock Pie firmware. LOS-17 ROMS need stock Pie blobs (drivers), while the older LOS-16 ROMs need stock Oreo blobs (drivers).
That's the most common reason for what you describe and fits the timeline of you not having the phone in your hands for several months.
Yes, you do need to flash Magisk with the custom ROM and usually GAPPs as well. (Although a few ROMs come with their own GAPPS.)
Here's current LOS-16 ROM if you want to try that:
XDA THREAD:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
DOWNLOAD:
https://github.com/ShapeShifter499/...ses/tag/lineage-16.0-20200716-h930_oreo-blobs
That dev makes new builds almost every day -- both for universal "H930" (all variants except T-mobile H932) and also builds specifically for T-mobile H932. That download link is for 07/16 daily build for "H930".
But there is still the matter of the account: FRP doesn't go away just by wiping in TWRP or flashing a different ROM, as far as I know.
The best solution would have been too simply log in with the previous account, then delete the account in the OS. That would release the FRP.
If you manage to boot any ROM, I would do that first thing. If your friend is far away, then give him a call. He could temporarily change his Google password to something simple, give it to you, then change it back once you have removed his account from the phone.
Edit: maybe flashing with LGUP Refurbish mode clears FRP. Do you know that, @ChazzMatt.
ChazzMatt said:
What was the previous ROM? If it was LOS-16 based, you can't replace with LOS-17 based ROM without first flashing stock Pie firmware. LOS-17 ROMS need stock Pie blobs (drivers), while the older LOS-16 ROMs need stock Oreo blobs (drivers).
That's the most common reason for what you describe and fits the timeline of you not having the phone in your hands for several months.
Yes, you do need to flash Magisk with the custom ROM and usually GAPPs as well. (Although a few ROMs come with their own GAPPS.)
Here's current LOS-16 ROM if you want to try that:
XDA THREAD:
https://forum.xda-developers.com/lg-v30/development/rom-lineageos-16-0-lineageos-17-0-wip-t4042333
DOWNLOAD:
https://github.com/ShapeShifter499/...ses/tag/lineage-16.0-20200716-h930_oreo-blobs
That dev makes new builds almost every day -- both for universal "H930" (all variants except T-mobile H932) and also builds specifically for T-mobile H932. That download link is for 07/16 daily build for "H930".
Click to expand...
Click to collapse
Is there an easy way to use that manifest? Normally it's just a ZIP file you need to flash. What it says in that guide looks like rubbish to me
Sorry for being a complete noob
BobberK said:
Is there an easy way to use that manifest? Normally it's just a ZIP file you need to flash. What it says in that guide looks like rubbish to me
Sorry for being a complete noob
Click to expand...
Click to collapse
Normally just go here and click on the heading of the build you want. At least on PC it starts a download. If it's not triggering a download make sure your pop up blockers are disabled. Unless something has changed there recently. @ShapeShifter499?
https://github.com/ShapeShifter499/LG_v30-LineageOS_Manifest/releases
Do NOT choose any T-Mobile H932 builds, since you don't have that model.