Related
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.
If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.
Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app
Hello,
I rooted and unlocked my HTC Desire 510 (Cricket) ages ago and I have an update for security patches which I cannot run because my phone just keeps rebooting into TWRP recovery and therefore does not install the latest update. I heard you have to flash the phone back to stock ROM but I'm not sure how to go about doing that. I am willing to restore my phone back to 100% stock if anyone knows how I can do that.
Thank you.
You have to relook the bootloader
Flash stock rom
Apply your ota updat
And after you can unlook again and flash recovery
mobbdeep said:
Hello,
I rooted and unlocked my HTC Desire 510 (Cricket) ages ago and I have an update for security patches which I cannot run because my phone just keeps rebooting into TWRP recovery and therefore does not install the latest update. I heard you have to flash the phone back to stock ROM but I'm not sure how to go about doing that. I am willing to restore my phone back to 100% stock if anyone knows how I can do that.
Thank you.
Click to expand...
Click to collapse
IMO.... Update isn't worth the time involved needed to install it. Installed on my wife's totally out of the box stock 510....esy,but couldn't really see a difference. Left my rooted nonsense ROM alone. It's been quite a while now and haven't noticed a difference. Your call, that's just my two cents worth
CSP III said:
IMO.... Update isn't worth the time involved needed to install it. Installed on my wife's totally out of the box stock 510....esy,but couldn't really see a difference. Left my rooted nonsense ROM alone. It's been quite a while now and haven't noticed a difference. Your call, that's just my two cents worth
Click to expand...
Click to collapse
I ended up finding someones stock recovery image dump around here after doing some searching and it worked out fine. The only reason I ever actually rooted my device was to use Helium to do full backups of my phone such as Apps and App Data.
Alright, I'm in need of some help, and I'm not sure if this is the right place to put this thread, so if it';s in the wrong place, I'm sorry for taking up space in the wrong section.
My issue is with my Nexus 6, the Verizon variant; I had a custom kernal, running 6.0, and was rooted. I wanted to upgrade to 6.0.1, and downloaded the newer version of the ElementalX kernal, the one I was using, as well as the necessary SuperSU files. I downloaded the new Android version, installed it, and before it went intoi the OS, I flashed the kernal and SuperSU upgrade, and now my phone either won't boot, or is taking the longest time for a phone to boot on the planet.
I need to download a 6.0.1 ROM that I can flash with TWRP. Any links or advice anyone could offer would be grately appreciated, because right now, I'm drawing a massive blank.
Many thanks!
Do you need to backup any data?
Could you not just flash a stock "like" rom such as this one by Danvdh http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493 as it has already been rooted.
I have been running it for a while, very solid and stable rom.
Which SuperSU did you install?
Reflash the rom youre using and then flash Super su (asuming its not a pre-rooted rom) BEFORE flashing elemental x. Other kernels work the other way around
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
I decided to download and flash a custom CM13 build, but it's a bit finicky, kinda to be expected with an early release, though. I'm using that ROM, for now. I'd still prefer getting something from the CM team, something that's supported and I can download upgrades to.
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
holeindalip said:
Which SuperSU did you install?
Click to expand...
Click to collapse
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
swazii said:
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
Click to expand...
Click to collapse
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
DaJesuZ said:
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
Click to expand...
Click to collapse
2.61 is old now, 2.65 is the latest.
DaJesuZ said:
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
Click to expand...
Click to collapse
Sounds to me like you dont have the correct bootloader. Which bootloader are you currently using? try flashing the newest bootloader and radio then flash your rom again. It should then boot up fingers crossed.
Jnewell05 said:
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
DaJesuZ said:
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
Click to expand...
Click to collapse
Why did you flash gapps? It seems that this rom comes with gapps already.
blanco2701 said:
Why did you flash gapps? It seems that this rom comes with gapps already.
Click to expand...
Click to collapse
Wouldn't let me use the Play Store. Nothing would install, and it's kinda pointless to have an internet-capable device if it can't connect to what's supposed to provide me with that internet connectivity (downloading Chrome, for example). Had to flash stock gapps, but it all seems to be working now.
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
forvrknight said:
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
Click to expand...
Click to collapse
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Wolf2231 said:
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Click to expand...
Click to collapse
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
forvrknight said:
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
Click to expand...
Click to collapse
I see you went through a lot. Well the possibility of one of us getting this problem is low, under same consequences. Anyways, on this page, we just try to share info between each other to find the best solution. That's what its about.
Hey, thanks for sharing your experience you just added a possible problem and solution. This will be helpful for the community. About md5 google how to check it. There are really easy ways. Checking the md5 is worth it, that's for CM ROM. I believe LGUP does check for kdz automatically, since the kdz are stock.
Good luck, and don't stop sharing.