Ah yes, wasnt thinking windoze funny since of course it was a bat file
Just had to give you a hard time cause I knew you were thinking mac/linux. At some point I may add one but we'll see.
Posted 18 June 2014 - 04:37 PM
Ah yes, wasnt thinking windoze funny since of course it was a bat file
Just had to give you a hard time cause I knew you were thinking mac/linux. At some point I may add one but we'll see.
Non potest esse nisi unus
Posted 18 June 2014 - 05:06 PM
Yes I was. Must of had something to do with the corrupt partition. After I downgraded to 9.30.1 (without further problems I might add) the root script worked fine with exception of the TWRP-2.7.1.0 would not work (it would load but screen was frozen). I used TWRP-2.7.0.0 and it worked fine.
I'm downgraded, unlocked, rooted with recovery and grateful for your help. Thank you.
Well I spoke too soon. I can't get a ROM to flash using the TWRP that I installed. I don't know why,Just hangs at the Rom's boot logo. So I'm going back to stock KitKat for now.
Posted 19 June 2014 - 06:24 AM
Only CM11 has a "test" rom out there AFAIK. I tried a few that have 4.4.2 in their title but none worked. Tried LiquidSmooth 3.1 and ParanoidAndroid and gave up. Didnt try PacMan yet.
Posted 19 June 2014 - 06:26 AM
Only CM11 has a "test" rom out there AFAIK. I tried a few that have 4.4.2 in their title but none worked. Tried LiquidSmooth 3.1 and ParanoidAndroid and gave up. Didnt try PacMan yet.
There is a PAC Alpha that boots and has the same issues the CM build has (which makes sense)
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
Posted 20 June 2014 - 05:31 AM
Thanks! This is awesome!
Posted 21 June 2014 - 11:55 AM
Non potest esse nisi unus
Posted 21 June 2014 - 12:00 PM
Well I will try not too, but you know me... Take it easy.I'm on vacation for a week. Don't break stuff while I'm gone.
Sent from my GT-I9505G using Tapatalk
Posted 21 June 2014 - 12:13 PM
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
Posted 21 June 2014 - 05:38 PM
No not yet and it would only be the second time if I did lol...Third times a charm? You broke it already
Sent from my S-Offed One M8
Posted 21 June 2014 - 05:40 PM
Posted 22 June 2014 - 07:30 AM
I get...'load_file: could not allocate' and 'Error loading system.img'.
When it reboots, I only get the boot logo, then it turns back off. Doesn't seem to be a way to get back to the boot menu either.
Suggestions?
Posted 22 June 2014 - 07:45 AM
My suggestion would be to provide a ton more info than that....what did you have before you borked something, what were you doing or trying to do when you borked, etc.
Sams on PTO and no one like to play guessing games
Hopefully one of the others can help you, because I am off for some twisties in the canyons.
Posted 22 June 2014 - 08:03 AM
My suggestion would be to provide a ton more info than that....what did you have before you borked something, what were you doing or trying to do when you borked, etc.
Thanks @cmh714.
As an update...I've been able to get back to FASTBOOT menu, and have tried Full, Keep-Data, and Universal; all result in the folling errors...
load_file: could not allocate
error: cannot load 'system.img'
I'm not certain what else to provide. Below is the full process. I followed all the steps. It possibly sounds like there's not enough room to load the img onto the phone?
Since I ran Full, I'll already need to restore my data, so maybe I could do a FDR at this point? If so, how, as I can't get to recovery, only FASTBOOT.
Posted 22 June 2014 - 09:04 AM
I was able to get to recovery mode and complete FDR (full wipe). However, still only getting to boot logo, then the phone shuts off.
After re-running the FXZ flashing process for my 4.4.2 FXZ, I still get the following error, and it only boots logo and powers off.
load_file: could not allocate 1135269260 bytes
error: cannot load 'system.img'
Posted 22 June 2014 - 09:53 AM
Sounds like you're using the wrong fastboot. You need the Moto fastboot because of the size of the system file. Search for mfastboot.exe, or make sure your using the correct fastboot files from the OP.I was able to get to recovery mode and complete FDR (full wipe). However, still only getting to boot logo, then the phone shuts off.
After re-running the FXZ flashing process for my 4.4.2 FXZ, I still get the following error, and it only boots logo and powers off.
load_file: could not allocate 1135269260 bytes
error: cannot load 'system.img'
Posted 22 June 2014 - 11:54 AM
Sounds like you're using the wrong fastboot. You need the Moto fastboot because of the size of the system file. Search for mfastboot.exe, or make sure your using the correct fastboot files from the OP.
I am using the files presented by the OP, though the fastboot name is 'fastboot', not mfastfoot.
I have also attempted to use mfastboot v2 (renamed to fastboot), but I get the error...'(bootloader) Variable not supported!', in addiiton to...
load_file: could not allocate 1135269260 bytes
error: cannot load 'system.img': Not enough space
Though I ran a FDR, is it possible that it did not work due to 4.4.2 files flash attempt, and there's really not enough room? I've tried running the 4.1.2 ver, but it seems some of the 4.4.2 process did overwrite some files and FASTBOOT tells me a security issue.
Posted 22 June 2014 - 12:06 PM
Posted 22 June 2014 - 12:13 PM
Posted 22 June 2014 - 12:47 PM
It's it possible you do not have enough space on your drive? In order to flash the system file, fastboot will break it into several chunks, so you need to have enough free drive space for it.
No, I have plenty of HDD space. Wonder if it's a disk issue, though. I'll try moving all to another disk and re-running.
Posted 22 June 2014 - 12:47 PM
Either of those examples could be an issue, but I dont think you need to get moto-fastboot. Pretty sure Sam provided everything. Granted I am on a Mac but fastboot for Darwin chunked up the system image into little pieces, would imagine the same for Win and Linux.
I think you need to regenerate your scripts based on the new FXZ files you extracted for KK
0 members, 9 guests, 0 anonymous users