Hi guys! I just had got the Photon Q today and successfully got it rooted and successfully got a custom recovery installed on it. The problem is with EVERY ROM i've tried flash, it fails to install properly and aborts the installation. I've tried on both CWM and TWRP, but the result is the same and wont install. Does this have to do with the fact that the ROMs got unified for the multiple Motorola devices? I'm about to try older nightly builds i've found, just so I can have my phone on KitKat. Anyone have any ideas why every ROM is failing to install??
Well, CWM might fail if you are using an older version... However, the latest TWRP should work fine.
What's the error message? Are yo using the latest version?
arrrghhh said:
Well, CWM might fail if you are using an older version... However, the latest TWRP should work fine.
What's the error message? Are yo using the latest version?
Click to expand...
Click to collapse
Yup, i'm using the latest version, 2.7. Anyway, I got it figured out and realized it was my SD card, so I just flashed the ROMs from internal storage instead and it worked fine.
But now i'm having a new problem. Now i'm not getting any service and wifi wont come on. I've flashed custom roms on other phones before and i've never had this problem. It's like this on Carbon, Mokee, and now Cyanogen. I'm gonna keep browsing the forum for some ideas, do you have any idea by any chance?
KoolBurnX8 said:
Now i'm not getting any service and wifi wont come on. I've flashed custom roms on other phones before and i've never had this problem. It's like this on Carbon, Mokee, and now Cyanogen. I'm gonna keep browsing the forum for some ideas, do you have any idea by any chance?
Click to expand...
Click to collapse
This sounds like a result of deleted or formatted /persist partition.
Have you done it? Do you have a backup?
kabaldan said:
This sounds like a result of deleted or formatted /persist partition.
Have you done it? Do you have a backup?
Click to expand...
Click to collapse
Yup, I had a back up, but it failed to restore. I had to go back to stock because I couldn't figure out how to get back my service and wifi for the life of me. I still want to use Carbon, but i'm afraid it'll just go back to no service and no wifi again. Good thing about the stock rom, it seems to update your network profile and PRL for you.
KoolBurnX8 said:
Yup, I had a back up, but it failed to restore. I had to go back to stock because I couldn't figure out how to get back my service and wifi for the life of me. I still want to use Carbon, but i'm afraid it'll just go back to no service and no wifi again. Good thing about the stock rom, it seems to update your network profile and PRL for you.
Click to expand...
Click to collapse
You must be on the stock ROM to update the PRL. Make sure everything works & is updated before flashing a custom ROM.
arrrghhh said:
You must be on the stock ROM to update the PRL. Make sure everything works & is updated before flashing a custom ROM.
Click to expand...
Click to collapse
So I got it back to stock, then just tried the nightly of Pac man rom. It flashed fine, and my data and service are working. It's just my wifi is blacked out now and wont let me turn it on. Any ideas?
KoolBurnX8 said:
So I got it back to stock, then just tried the nightly of Pac man rom. It flashed fine, and my data and service are working. It's just my wifi is blacked out now and wont let me turn it on. Any ideas?
Click to expand...
Click to collapse
Which nightly are you running of PAC? Any logs?
arrrghhh said:
Which nightly are you running of PAC? Any logs?
Click to expand...
Click to collapse
pac_moto_msm8960_4.4.Alpha-1_20140409-051845
The ROM is great I don't wanna go back to stock
Hopefully you mean my recovery log
KoolBurnX8 said:
pac_moto_msm8960_4.4.Alpha-1_20140409-051845
The ROM is great I don't wanna go back to stock
Hopefully you mean my recovery log
Click to expand...
Click to collapse
Is that from flashing PAC...? I don't see anything there from being flashed.
I assume the ROM boots fine if you say data and service are working. I mean logs from Android, like logcat and dmesg.
arrrghhh said:
Is that from flashing PAC...? I don't see anything there from being flashed.
I assume the ROM boots fine if you say data and service are working. I mean logs from Android, like logcat and dmesg.
Click to expand...
Click to collapse
Yeah that was after flashing PAC ROM. I was finally able to do a good wipe of everything and finally got PAC running smoothly. The newest TWRP 2.7.0.1 wont let me do a good wipe, so I had to use 2.3.3.1 to do the wipe. Those versions wouldnt flash the ROMs properly and would fail, so I installed the newest TWRP 2.7.0.1 (again) and now all the ROMs i've flashed work great.
KoolBurnX8 said:
Yeah that was after flashing PAC ROM. I was finally able to do a good wipe of everything and finally got PAC running smoothly. The newest TWRP 2.7.0.1 wont let me do a good wipe, so I had to use 2.3.3.1 to do the wipe. Those versions wouldnt flash the ROMs properly and would fail, so I installed the newest TWRP 2.7.0.1 (again) and now all the ROMs i've flashed work great.
Click to expand...
Click to collapse
I read your other post, that is odd. Not sure why you would have to revert to an older version of TWRP... Actually I'm a bit behind, I'm still on 2.6.3.1 I think. Not sure upgrading my phone would be a good test, since you proved moving from an older to newer version works...
Hmmm. I might just RSD Lite back to stock to see if I can recreate this.
Related
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
try formatting system after the data wipe, then flash rc7.
dmalikyar said:
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
Click to expand...
Click to collapse
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
droidstyle said:
try formatting system after the data wipe, then flash rc7.
Click to expand...
Click to collapse
Tried that and it made no difference.
dmalikyar said:
Tried that and it made no difference.
Click to expand...
Click to collapse
try using odin......just remember after you odin back to the root66 image, you have to reinstall CWM and doesn't hurt to make sure ur bootloader is unlocked using the 1.2 version of the ez unlock then flash again
digitalsynner85 said:
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
Click to expand...
Click to collapse
I'll try the Odin route. I'll go back to root66 and try it from there.
dmalikyar said:
I'll try the Odin route. I'll go back to root66 and try it from there.
Click to expand...
Click to collapse
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
digitalsynner85 said:
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
Click to expand...
Click to collapse
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
imklaho your
droidstyle said:
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
Click to expand...
Click to collapse
I Odin'd root66 and installed the ez unlocker as well as clockworkmod via rom manager. I went into recovery and wiped data/factory reset/wiped cache/wiped dalvik cache. I then installed LS RC7. It went through the installation and indicated that it completed. After I reboot, I briefly see the Samsung logo, then the screen is completely black. No boot animation. I let it set for over 20 mins. and nothing happens. This is absolutely bizarre. I've tried 3 different downloads. I'm at a loss. Is there a way to convert the zip to an img and odin it on?
KT747-Kernel-AOSP-JB-VZW-10-31-2012.zip
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
dmalikyar said:
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
Click to expand...
Click to collapse
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
dmalikyar said:
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
Click to expand...
Click to collapse
Have you tried TWRP recovery as opposed to CWM?
shangrila500 said:
Have you tried TWRP recovery as opposed to CWM?
Click to expand...
Click to collapse
I installed twrp and I really like the interface but it didn't resolve the issue of flashing RC7. I've installed paranoid android and can install aokp and cm10 with no problems. I can't install RC7 or slim beans.
Cannot install Liquid Smooth
Yah the guy at Liquid Smooth is kind of a butt wipe. I understand the desire to have a screen capture and a logcat but if the user can't even install the flash how is a screen capture going to help. Maybe a logcat could. But either way why be an A hole about it.
I am having the same issue, I even formatted my system and still LiquidSmooth says it flashed but it just refuses to boot. I have used Odin to install the stock JB 4.1.1 from Poland but I still get the same problem. I do believe it has something to do with having tried CaponMod4NSS_3.0 the day before. Still I would think formatting the system would resolve that.
Any ideas? I will try to install the Samsung 4.1 ROM with Odin to see if that helps.
I much prefer AOSP over TW; however, it is hard to tolerate due to random reboots. What exactly can be causing this? I tried different CPU governors and everything. To my knowledge, this started occuring after I got my new battery, the gorilla gadgets 4500 mah.
If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.
Chris123NT said:
If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.
Click to expand...
Click to collapse
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.
LegoFarmer said:
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.
Click to expand...
Click to collapse
Should I try updating my bootloader? This was rooted and unlocked back in October, so it may not flash modern (4.2.2) roms correctly. What do you think?
Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.
Chris123NT said:
Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.
Click to expand...
Click to collapse
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?
Chris123NT said:
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?
Click to expand...
Click to collapse
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.
LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
LegoFarmer said:
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.
Click to expand...
Click to collapse
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.
Chris123NT said:
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.
Click to expand...
Click to collapse
What happens is I use the recovery hotkeys, but the screen is black unless I release the hotkeys, in which it just boots normally
Fixed lol. I had to let go of the power button after it vibrated. I can take it from here, thanks, man!!!
Ok so I have quite a strange problem. Whenever I try to reboot my phone, either from holding the power button and choosing the "reboot" option on the screen, or by turning the phone off physically, and then turning it back on, my phone does not boot. When I try to turn it on, it shows the Samsung image, and then the screen turns black and nothing happens afterwards. The only way I found around this, is that I have to put my phone into recovery and then do a factory reset.
Currently, I'm running BeanStalk v4.3.1009, but I've also flashed the latest version of Slimbean and the samething happens. I used Odin to flash back into the stock Rogers GB firmware and I've gotten the phone to successfully reboot.
I then flashed Beanstalk and I was again unable to successfully reboot the phone.
Any ideas what's going on? I'm using TWRP v2.5 and then updated to v2.6 after going back to the original Rogers GB firmware, if that matters.
bluecrush69 said:
I'm using TWRP v2.5
Click to expand...
Click to collapse
This is the problem.
Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.
bluecrush69 said:
Should I be using CWM? I updated to TWRP 2.6.3 and flashed the roms, but I'm still getting the same issue when trying to install the latest version of Slimbean/Beanstalk. The problem doesn't occur if I try an older version of Beanstalk though.
Oh well, I'll just stick with the version that's working for me.
Click to expand...
Click to collapse
Flash it once with cwm. That'll clear things up then you can go back to twrp
jd1639 said:
Flash it once with cwm. That'll clear things up then you can go back to twrp
Click to expand...
Click to collapse
Can someone explain what's technically wrong with twrp 2.6.3 I've flashed a ton of these 4.3 Roms without issue. Why is everyone saying it's bad?
Sent from my XT1080 using Tapatalk
Well I have been a CWM(and sometimes also TWRP) user for years. But I am stumped. I recently started having issues staying connected to AIO/Cricket(voice not even staying connected). As I am running a custom ROM I decided to try Stock and see if the problem persists, thus it may be a hardware issue with the radio or something. So I did a current backup, and restored one from a few weeks back. It's the same ROM but I thought it was worth a shot. It restored fine but the problem persisted. Then I decided to restore my new backup from the hour before. It failed. Gave me an MD5 Mismatch error(I think I have that right). So I made another new backup, same thing. I am unable to restore any backups made right now. I can still restore the one from a few weeks ago. I am running the very latest CWM touch. I tried flashing TWRP to see if that might help(using Rom Manager to do so). This has always worked before. It said that it works, and even tells me it's rebooting into TWRP when I reboot to Recovery. But the broken version of CWM is still what is loading. I am at a loss here.
your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).
simms22 said:
your issue here is that you are using rom manager. rom manager doesnt fully work, it is broken, stop using it. you can flash a new recovery the right way, via fastboot. you can also flash twrp using the flashify app(yes, it works).
Click to expand...
Click to collapse
Thank you! Gonna try flashing TWRP that way now!
Landara said:
Thank you! Gonna try flashing TWRP that way now!
Click to expand...
Click to collapse
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
First thing I did. I was able to backup with TWRP. Since I am currently running the restore from that NANDROID from a few weeks ago, it's all good! I am restoring the TWRP i just made, just to be sure. Seems to be restoring fine though. With my NANDRIOD problem solved, I can work on getting this radio issue fixed. I am really hoping it's just ROM related and I can salve it by flashing something else. I'm going to flash STOCK and see if it persists now.
simms22 said:
btw, i highly doubt that twrp will be able to restore a cwm backup. but if you have space on your device, it should at least create a backup.
Click to expand...
Click to collapse
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?
Landara said:
Actually one fast question, if I may. Would it be at all risky to flash the stock radio onto a custom ROM? That seems the easiest fix, if it is a fix at all. I downloaded the correct stock radio for my 820 from here:
http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523
If I just flash it over Nikxus would there be a problem?
Click to expand...
Click to collapse
no problem, in stock or custom roms the radios are the same
simms22 said:
no problem, in stock or custom roms the radios are the same
Click to expand...
Click to collapse
Thanks!
When I found out that Towel Root can finally root my 4.4.2 LG G2 (D801) from T-Mobile I was very excited to try it, so I went ahead and installed it. It worked of course, very well. so I continued to install Autorec, which restarted into TWRK Recovery. Great!
I wipe Dalvik & Cache and flash the Stable Cyanogen 10.2 rom from 2013, and now it's stuck on boot. Also tried with the latest nightly to same outcome.
What am I missing here?
yoerz said:
When I found out that Tower Root can finally root my 4.4.2 LG G2 (D801) from T-Mobile I was very excited to try it, so I went ahead and installed it. It worked of course, very well. so I continued to install Autorec, which restarted into TWRK Recovery. Great!
I wipe Dalvik & Cache and flash the Stable Cyanogen 10.2 rom from 2013, and now it's stuck on boot. Also tried with the latest nightly to same outcome.
What am I missing here?
Click to expand...
Click to collapse
CM builds use JB kernel and baseband. You'll need to find the right JB baseband for your phone and flash it and then the CM build you want to use.
AyDee said:
CM builds use JB kernel and baseband. You'll need to find the right JB baseband for your phone and flash it and then the CM build you want to use.
Click to expand...
Click to collapse
What's a baseband? and what do I "do" with it once I find it?
yoerz said:
What's a baseband? and what do I "do" with it once I find it?
Click to expand...
Click to collapse
Baseband is your modem. Install the zip in recovery before installing your rom. Install baseband/modem, full wipe, install rom.
You should find what you need here> http://forum.xda-developers.com/showthread.php?t=2451426
I suggest you read up on this stuff a little to get more familiar.
AyDee said:
Baseband is your modem. Install the zip in recovery before installing your rom. Install baseband/modem, full wipe, install rom.
You should find what you need here> http://forum.xda-developers.com/showthread.php?t=2451426
I suggest you read up on this stuff a little to get more familiar.
Click to expand...
Click to collapse
The only problem is, I can't do a full wipe because I have to keep the ZIP files of Cyanogen Mod and Gapps on the device. There is no way to load them on the device when in TWRP.
Also, that post is very confusing. It has a list of roms, and then a download link to a completely different list. How do I know which download correlates with:
D801BK (T-Mobile USA)
D80110C
M8974A-AAAANAZM-1.0.190034
by QUALCOMM, Incorporated Aug 10 2013
Is it LGD801_10C_RADIO.zip ??
AyDee said:
Baseband is your modem. Install the zip in recovery before installing your rom. Install baseband/modem, full wipe, install rom.
You should find what you need here> http://forum.xda-developers.com/showthread.php?t=2451426
I suggest you read up on this stuff a little to get more familiar.
Click to expand...
Click to collapse
OK I tried again, flashed LGD801_10C_RADIO.zip before the Cyanogen zip, then Gapps and Supersu, restarted and it's doing the same thing. Cyanogen screen loading animation but never booting up.
Like I said before, I CANNOT do a full wipe in TWRP because that will delete all the ZIP files on the device. This device does not have an SD card I can load them on and the USB connection doesn't work (driver not found, this is apparently a known bug).
yoerz said:
OK I tried again, flashed LGD801_10C_RADIO.zip before the Cyanogen zip, then Gapps and Supersu, restarted and it's doing the same thing. Cyanogen screen loading animation but never booting up.
Like I said before, I CANNOT do a full wipe in TWRP because that will delete all the ZIP files on the device. This device does not have an SD card I can load them on and the USB connection doesn't work (driver not found, this is apparently a known bug).
Click to expand...
Click to collapse
With TWRP can't in the wipe section you do an advanced wipe and just not select internal storage, thus leaving the ROM on your phone while still doing a full wipe?
TheBestEver said:
Full wipe means the "factory reset" option in TWRP. You're on kitkat bootloader. You need to somehow find a flsshable .zip of the jb bootloader. Modem doesn't matter. I've used JB and KK modem and both work. Maybe you're on stock KK kernel and need to flash the JB kernel? If you're on KK stock and want to jump to CM you should find a flashable .zip of both kernels or .IMG times and try that as well if option 1 doesn't work. Sorry
Click to expand...
Click to collapse
Where can I find that Kernel?
TheBestEver said:
Are you trying to flash CM 10.2 or CM11?
Click to expand...
Click to collapse
I tried both.
CM Stable-10.2.0-d801
and
CM 11-20140617-NIGHTLY-d801
yoerz said:
which restarted into TWRK Recovery. Great!
Click to expand...
Click to collapse
Is that where Miley needs to go? Typo of the day goes to you!
Goldie said:
Is that where Miley needs to go? Typo of the day goes to you!
Click to expand...
Click to collapse
Twrp.. Twrk.. whats the difference. You know what I mean.
yoerz said:
Twrp.. Twrk.. whats the difference. You know what I mean.
Click to expand...
Click to collapse
Well yeah obviously. This is why you were awarded "Typo of the day" and not "WTF of the day"
Sent from my SM-G900F using Tapatalk
yoerz said:
I tried both.
CM Stable-10.2.0-d801
and
CM 11-20140617-NIGHTLY-d801
Click to expand...
Click to collapse
Both of which still run 4.2 sources. Before u flash either , what must occur first is flash the 4.2 jb modem then Rom etc.
Sent from my LG-D801 using XDA Premium 4 mobile app
You might be able to help me, I root with TowelRoot (checked with Root Checker) and then installed/run AutoRec for T-Mobile d801. And it boot loop into download mode, (i have a package to fix that, but still have no Recovery)
yoerz said:
When I found out that Towel Root can finally root my 4.4.2 LG G2 (D801) from T-Mobile I was very excited to try it, so I went ahead and installed it. It worked of course, very well. so I continued to install Autorec, which restarted into TWRK Recovery. Great!
I wipe Dalvik & Cache and flash the Stable Cyanogen 10.2 rom from 2013, and now it's stuck on boot. Also tried with the latest nightly to same outcome.
What am I missing here?
Click to expand...
Click to collapse
You can find the KK modem in the SOKP thread in Development and that may help.