Develop Bugs

problem installing rom from fresh root

I am trying to install the ozzey ROM on my incredible I just got it and rooted it. I have Rom managr, astro file viewer and titanium backup installed. I know I can do it via update.zip or Rom manager but it always fails and says signature verification failed. I triple checked the file to see that it was in .zip not .zip.zip I had windows show the hidden file extensions. In Rom manager it says whole file verification failed along with signature file. Astro file viewer shows it as update and on the root of the SD card but still get the error. I haven't done nand unlock or backup, and I don't care about looking any apps its a new phone with nothing on it. Any suggestions or method instructions? Does the SD card have to be fat32? My SD card is the 2gb pny card. Thanks!

You should just be able to use the .zip, put it anywhere on your sd card. Boot into Clockwork Recovery (If you flashed the new recovery using reflash.exe from unrevoked), DO A NANDROID BACKUP (this is a full system backup), format the user data and cache partition (both options), select update with a .zip and select your preferred .zip file (in your case ozzeh's)
See here for more information and any questions: http://forum.xda-developers.com/showthread.php?t=709220

Any thoughts as to why I am getting those errors? Can I use the re flash tool and go into clockmode recovery and install througt that?

If you do not have clockwork recovery you're not going to be able to flash a ROM. You need to use the reflash tool before you can flash any ROMS.

i have clockwork recovery its on my phone but it still won't flash. Also I tried the reflash but it keeps saying that its interrupted, I uninstalled HTC Sync and it still doesn't work. I also tried to format the sd card to fat32 and ran clockwork recovery but it didnt work same error

It's not clear from your posts exactly what your error is. You say you have Clockworkmod Recovery installed but you keep referencing trying to flash from ROM Manager.
What happens when you boot into Recovery and try to flash the zip file from there?

I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed. I booted into it and it says it can't find the file in /cache/ and it says verification failed so it aborts and reboots.

kingdavid216 said:
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
You might want to try a different rom and see how it goes.

That makes no sense. You can't flash CWM Recovery from ROM Manager on the Incredible (although you can update a prior install, sort of); you have to use unrevoked's tool.

kingdavid216 said:
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
I thought I remember reading in some thread that ROM Manager going to clockworkmod will not work because there is no write access.
You will have to use recovery reflash tool to install the clockworkmod recovery and boot into it.
You can find that information in this thread:
http://forum.xda-developers.com/showthread.php?t=706270

supagene said:
I thought I remember reading in some thread that ROM Manager going to clockworkmod will not work because there is no write access.
You will have to use recovery reflash tool to install the clockworkmod recovery and boot into it.
You can find that information in this thread:
http://forum.xda-developers.com/showthread.php?t=706270
Click to expand...
Click to collapse
I instaleld Clockworkmod from ROM Manager, 2.0.1.3 is the verison of clockworkmod I have installed on the phone. I then use ROM Manager to install ROM SD card and it fails, it says signature verification failed and whole-file verification failed
Click to expand...
Click to collapse
You can use Rom manager to boot into clockwork recovery and install the zip from there however, you can't use the feature "Install rom from sd card" within rom manager itself.

Well I tried using just ROM manager to boot into clockwork and I was able to but it still gives me the same errors. I can't do the unevoked flash it reboots then says the communications were intruputed. I deleted HTC synch and had the usb on both disk drive connection and HTC synch but it doesn't go through

kingdavid216 said:
Well I tried using just ROM manager to boot into clockwork and I was able to but it still gives me the same errors. I can't do the unevoked flash it reboots then says the communications were intruputed. I deleted HTC synch and had the usb on both disk drive connection and HTC synch but it doesn't go through
Click to expand...
Click to collapse
Did you ever successfully use unrevoked's flash utility? If you just downloaded rom manager and booted in to recovery without successfully flashing, that won't work.
If you're having problems using the reflash tool then I suggest you get that working and then try again installing a rom.

Use terminal emulator to verify u have su.. Just type su and click accept, if u can do that follow word for word unrevoked reflash method, including installing the correct drivers for adb.
Sent from my ADR6300 using Tapatalk

i just did terminal emulator and i get root acess, #, superuser comes up and allows me to access it, so I will try again but for some reason I get that communication was interuppted.

hey, thanks to all you guys I finally got the custom ROM to work. I did the revoked flash, i had to delete the old htc driver and start again, and once it finally flashed just mounted the sd card and installed, worked perfectly, thanks again!!

kingdavid216 said:
hey, thanks to all you guys I finally got the custom ROM to work. I did the revoked flash, i had to delete the old htc driver and start again, and once it finally flashed just mounted the sd card and installed, worked perfectly, thanks again!!
Click to expand...
Click to collapse
glad you got it working!

Congrats man, good to hear you finally got it working.

[Q] Rom Manager - Failed to Seek

Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?

...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)

jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.

Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.

Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.

I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped

Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.

In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App

I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.

PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.

No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.

Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App

I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.

srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well

PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.

I've reached out to the developer. Hopefully we will hear from him soon.

Can you guys try clearing your download cache, and then reflashing recovery?

Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution

Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App

Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7

[Q] HBOOT Image and Update Script Errors

What I did:
Rooted Evo 4G Gingerbread using Revolutionary
Flahsed su-2.3.6.3-efgh-signed.exe and PC36IMG.EXE
Worked great, got excited flashed:
SOS_v1.9.0.2-swag.exe, navbar_rednblack.exe, remap_camera.exe, and ChopSuey-v.9.2.6-UNIVERSAL-signed.exe
Whats going on:
SOS, navbar, and remap flash fine; all other flash attempts give the error, E: Can’t Find Update Script
At HBoot
SD Checking
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
(With PC36IMG.EXE on the SD root) Also
Parsing (SD ZIP)
(1) Recovery
So how do I get rid of the errors so I can flash another ROM or whatever? Thanks for helping a noob

If you're already rooted, you need to boot into recovery. Then navigate to where the .zip (ROM) is located. The instructions to flash should be provided on the first page of the dev's post.

Thank you but, I don't undeerstand. I can find the zip files that I put on the SD card, and go into the recovery screen but when I try and flash any ROM/add on/bootanimation/ I get the eror, E: Can’t Find Update Script" so where is the script? Also, any ieas on the no/wrong image issue?

What recovery r u using? R u flashing chopsuey thru hboot or recovery?
Sent From My Pocket

I flashed the Kernal throu recovery.

HBoot> scroll to Recovery>hit power key> Brings up android systems recovery screen> scroll to "Flash sip from SDcard> Select the zip file. That is when I get the E: Can not find update script error.
I am not running the PC36IMG ROM, I am running the SOS_v1.9.0.2-swag but in HBOOT, its looking for the PC36IMG image, are't these issues related?

Google "evo amon-ra xda forums".
Download the PC36IMG.zip.
Copy and paste it in the root of your SD card.
Press volume up to install in hboot.
Once complete, boot into recovery and try to flash the ROM zip file.
Be sure to delete the amon-ra zip file or else it'll just ask if you want to flash when hboot loads.
Sent from my PC36100

Thanks, trie your suggestion but the file still aborted with the can find update script error.

Sounds like you got a bad zip file
Sent From My Pocket

i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"

alltoEZ said:
i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"
Click to expand...
Click to collapse
Go to the correct forum for your device. I'm sure someone over there will be able to help you do whatever it is you're trying to do.
If you're looking for a bootloader-flashable recovery file, I posted one in the TWRP thread for the LTE.

[Q] Help -- CWM not working

Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?

O's said:
Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.

a.s.j said:
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.
Click to expand...
Click to collapse
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -- installation failed, every time.
I've since gotten CM10.1 and Mimicry to work with CWM, but I'm struggling with one ROM in particular no matter the recovery: coolIOS, a 4.0.4.
Tried to install it with CWM 5.0.2.7 and got the error described at top.
Tried with CWM 6.0.4.5.
Tried with CWM Touch 5.8.1.0.
Tried with TWRP 2.6.3.0.
Same error, every time. Redownloaded the ROM, but same. I'm really at a loss with that one. It worked fine on a previous G2.

O's said:
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -
Click to expand...
Click to collapse
Just try to install 4EXT recovery !
http://4ext.net/

Kéno40 said:
Just try to install 4EXT recovery !
http://4ext.net/
Click to expand...
Click to collapse
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.

O's said:
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.
Click to expand...
Click to collapse
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf

a.s.j said:
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf
Click to expand...
Click to collapse
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.

O's said:
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.
Click to expand...
Click to collapse
SOLVED: Helps if I read the instructions. Thread for that ROM clearly says to have Desire Z hboot; I had G2 hboot. In all the years of using a G2, I've never had to switch hboot and was unfamiliar with it. If anyone else has same issues as this post, might try installing the Virtuous Team's PC10IMG.zip and read up on it at the Hboot thread. Thanks to all who beared with my lack of knowledge.

Bricked Note 8? Can't flash any Rom | Please Help! E: Unable to mount '/preload'

Hi!
I'm having a big problem with my Samsung Galaxy Note 8.0 N5110. I have installed a new rom using TWRP 2.8.7.0 recovery but now I can't change Rom because when i try to flash .zip files i get the following error:
E: Unable to mount '/preload'
But once flashed the new rom the tablet doesn't boot (I can see the Bootanimation but no more! And I have Wiped all data)
What is working:
Download mode accessible
Recovery accessible
I can flash files
What I noticed:
I can flash zip roms but I always get the mount preload error, I tryed to mount preload partition in my recovery settings but it doesn't mount!
Originally I have had this firmware: http://www.sammobile.com/firmwares/download/32115/N5110XXDNF1_N5110ITVDNF1_ITV/
Ok, I tried to download the stock rom from Sammobile (http://www.sammobile.com/firmwares/download/57737/N5110XXDNK1_N5110UVSDNK1_TPA/) but when i try to flash that with Odin I get the Failed! message.
I tryed to change recovery and to flash a new rom (Gnabo rom) but it doesn't finish booting.
I think that this is a partition problem and that I need a PIT file to restore them, i found this thread about this http://forum.xda-developers.com/showthread.php?t=2333191. I tryed to flash the file but i get Failed!
Now, I'm trying to download a new stock rom, I found this http://www.sammobile.com/firmwares/download/56156/N5110UEU2COI3_N5110XAR2COI3_XAR/ I hope it will work!
Please can someone help me?:crying::crying::crying::crying:

leofabri said:
Hi!
I'm having a big problem with my Samsung Galaxy Note 8.0 N5110. I have installed a new rom using TWRP 2.8.7.0 recovery but now I can't change Rom because when i try to flash .zip files i get the following error:
E: Unable to mount '/preload'
But once flashed the new rom the tablet doesn't boot (I can see the Bootanimation but no more! And I have Wiped all data)
What is working:
Download mode accessible
Recovery accessible
I can flash files
What I noticed:
I can flash zip roms but I always get the mount preload error, I tryed to mount preload partition in my recovery settings but it doesn't mount!
Originally I have had this firmware: http://www.sammobile.com/firmwares/download/32115/N5110XXDNF1_N5110ITVDNF1_ITV/
Ok, I tried to download the stock rom from Sammobile (http://www.sammobile.com/firmwares/download/57737/N5110XXDNK1_N5110UVSDNK1_TPA/) but when i try to flash that with Odin I get the Failed! message.
I tryed to change recovery and to flash a new rom (Gnabo rom) but it doesn't finish booting.
I think that this is a partition problem and that I need a PIT file to restore them, i found this thread about this http://forum.xda-developers.com/showthread.php?t=2333191. I tryed to flash the file but i get Failed!
Now, I'm trying to download a new stock rom, I found this http://www.sammobile.com/firmwares/download/56156/N5110UEU2COI3_N5110XAR2COI3_XAR/ I hope it will work!
Please can someone help me?:crying::crying::crying::crying:
Click to expand...
Click to collapse
UP

leofabri said:
UP
Click to expand...
Click to collapse
I've had such problem when tried to change partitions using this manual.
After I flashed modded PIT file I see that my partitions changed, but I couldn't restore backup or flash any ROM withour errors. Though TWRP 2.8.7.0 said "successful" I seen a lot of errors in log "E: Unable to mount '/preload' ". So when I try to boot my I777 I have bootloop on ROM logo, either SlimLP, CyanogenMod or CyanideL. I tried to repair\resize partition in TWRP with no luck. Odin and stock firmware is no help - it always fails because of partition. So I found original PIT file pulled out from stock ROM, flashed that PIT using Odin and now I can either flash stock firmware thru Odin or flash some kernel with custom recovery to flash custom ROMs. So my guess is to find such PIT file that will fix your issue.
Hope this help.
UPD: I was be able to install SlimSaber(KK 4.4.4), so I suppose if you getting "E: Unable to mount '/preload' " you can either flash original PIT or you can find ROM that don't use /preload partition.

Having A Tablet Stuck At Boot Logo Is A Serious Problem
It Happened Also To Mine But A Different Tablet
Its A Time Where I Just Have To Replace A Motherboard To Fix The Problem
I Know Its A Easy Repair But Its Also Expensive To Repair

Sent from my SM-N900V using XDA Free mobile app