Database Info

[Q] Problems with MD5 file trying to flash CD10 rom

I have an ATT HTC One X 2.20 Hboot 1.14 using twrp 2.4.1 and have been trying to install roms but continue to have an issue with the MD5 file. I have followed the instructions about flashing the boot.img of CM10 but it seems no matter what I do, it can't find the MD5 and says it is skipping MD5. I know just enough not to get out of a bootloop but I am quite new to this. The one odd thing I see is when I go to mount my phone in order to copy the CM10 zip file into the phone, the options I get are different than others I see online: Mount System (unchecked), Mount Data,(unchecked), Unmount Cache (checked), Unmount SD Card (checked). Any help would be awesome.

quick update; same problem
SWell, going through some of other posts and videos, I tried using goo manager to download the CM 10 zip file. But Im still stuck on boot loop. And it still says that the MD5 file was not found. I used the onexroot.com tutorial to root my phone and have superuser and twrp. Not sure what else to try. Ideas on other stable JB roms I could try? Thanks again.

In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?

force check
redpoint73 said:
In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?
Click to expand...
Click to collapse
I'm pretty sure I do. I have always left it unchecked. Should I check it and try again?

I've always left it unchecked (no MD5 check). If its a bad download, all that will happen is the phone will get stuck on boot, anyway.
I'd go into TWRP, and see if its checked or not. And if so, uncheck and try to flash again.

Update: No Luck
I just tried wiping system, factory reset, and cache, flashing the cm10 boot.img and then installing the CM10 zip file and checking the force MD5 and then the entire process and unchecking the force MD5 and with both attempts I get right back to the same issue. All I can say is that I'm so thankful that I created a backup in twrp. I've restored my phone at least 20 times today, haha. Learning is definitely a process. Ill take any more ideas.

Download the ROM again, may just be a bad download.

Will try
I will try to download the rom again from the CM website. If I were to try another rom (viper xl), the process should be the same correct? Thanks for the help.

alemcc said:
If I were to try another rom (viper xl), the process should be the same correct?
Click to expand...
Click to collapse
Put the ROM on your SD.
Boot into hboot, go into TWRP
In TWRP, factory reset, wipe cache, wipe Dalvik
Install ROM
Reboot
ViperXL should flash boot.img in AROMA, although its not foolproof. If the phone doesn't boot (may take about 5 min first time), then flash boot.img using fastboot.
For most ROMs, you will need to flash boot.img manually. ViperXL is one of the few exceptions (also CleanROM 5.1, I think).

Still no luck
I just tried aokp JB 4.1 with no luck. I do everything I've been told or that I have read on these forums (copy zip to SD, flash boot image, install rom...) but i continue to get the same problem: MD5 not found, skipping MD5 and so on. If anyone has any ideas I'll be happy to give any other info needed. At this point I have a rooted phone but cannot install roms. Argh!

He's not the only one. I'm on viper 3.2.3 but when trying to flash any Rom based off of AOSP or anything similar I bootloop. Yes I flash the boot.img then the Rom to no avail . I started a thread in this department called weird problem if the OP would like to take a look there.
Sent from my HTC One X using xda app-developers app

I'm new to all this, but I don't understand why certain people have this issue but most don't. Aren't all att one x phones pretty much the same?

Same thing i'm wondering
Sent from my HTC One X using xda app-developers app

you dont check any md5 checking for custom roms in twrp
you only rom i know of that you will have a md5 without anything selected is evervolv 4.2 i found a fix where you copy the CERT.SF from evervolv 4.1 to evervolv 4.2 and it will install and boot.
also always remember to "fastboot flash boot boot.img" if you are on hboot 1.14 or newer. if you going changing from sense to aosp always do full wipes no matter what. never factory reset in bootloader.

Yes I've done this countless times as I was on jellybam before going to jokers sense 4+ Rom then viper . I know the processes but something is wrong.
Sent from my HTC One X using xda app-developers app

alemcc said:
I used the onexroot.com tutorial to root my phone and have superuser and twrp.
Click to expand...
Click to collapse
I hate websites like that one. They just ripoff content from XDA, repackage it, and give little or no credit to the actual developer or XDA.
Stupid question, your bootloader is unlocked, right? In bootloader, it says UNLOCKED?
It must, for you to have TWRP. But it doesn't hurt to cover all the possibilities.

[Q] this is a hercules

I'm running into an issue. I have at&t skyrocket (i727). I am trying to flash a rom but every time to try, it aborts. There's a message that says, "This package is for sch-i727 devices; this is a hercules"
Any advice on how to proceed?
thanks in advance.

Are you sure you don't have a t989?

jd1639 said:
Are you sure you don't have a t989?
Click to expand...
Click to collapse
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.

cov3nant said:
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.
Click to expand...
Click to collapse
In settings, about phone what model numbers shows up?

jd1639 said:
In settings, about phone what model numbers shows up?
Click to expand...
Click to collapse
If i recall, it says sch-i727 but i am having trouble restoring my backup.

cov3nant said:
If i recall, it says sch-i727 but i am having trouble restoring my backup.
Click to expand...
Click to collapse
Model says i727. I restored original stock firmware via Odin.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Same Problem
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727

swapnilps said:
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727
Click to expand...
Click to collapse
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!

Done!
FriedrichEngels said:
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!
Click to expand...
Click to collapse
Tried with latest recovery!!!
..and done!

[RESOLVED] Updating HBoot

Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.

zodac01 said:
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
Click to expand...
Click to collapse
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)

ayyu3m said:
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
Click to expand...
Click to collapse
Ha, a nice strong "no". Thank you for that - good thing I came here to check first then.
Ok, first things first, I've tried updating using the OTA, but it doesn't install. I'm using TWRP v2.6. I could get the error code, but I think I read somewhere that you can't (or shouldn't) install OTA with custom bootloaders? I was hoping to use CM if possible anyway, so hopefully shouldn't have to worry about that (unless that's the way to update the HBoot...)
As for the other info, my HBoot is v1.13 and my CID is O2___01.

807 94346552
Anyone with any information?

zodac01 said:
Anyone with any information?
Click to expand...
Click to collapse
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.

rosswhite said:
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
Click to expand...
Click to collapse
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?

zodac01 said:
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
Click to expand...
Click to collapse
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?

rosswhite said:
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
Click to expand...
Click to collapse
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.

zodac01 said:
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
Click to expand...
Click to collapse
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.

zodac01 said:
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
Click to expand...
Click to collapse
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville

rosswhite said:
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
Click to expand...
Click to collapse
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.

zodac01 said:
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
Click to expand...
Click to collapse
No problem at all, glad you got it sorted.

Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!

c1aran said:
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
Click to expand...
Click to collapse
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Sent from nowhere over the air...

Rapier said:
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
LINK REMOVED
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hi,
I got a bit frustrated last night and must have missed that information in the CM11 thread. I had a look at that link and it has fixed my issues. Thank you very much!

TowerRoot + Autorec + Cyanogen Mod

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.

[HELP THREAD] cm-13 on gt-p5100

Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.

Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/

killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi

HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next

killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.

billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!

killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html

killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.

billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.

killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?