n00b
Posted 22 June 2014 - 12:48 PM
You are using the wrong xmls for the fastboot commands. The system.img was renamed system.img.ext4 in some of the updates. So you need to rerun the script creator again in the 907fxz directory to create the right ones Sent from my VS980 4G
Not certain I understand. Do I need to rename 'system.img' to 'system.img.ext4', then re-run the script generator?
Tech Service & Beyond
Posted 22 June 2014 - 12:50 PM
Also FYI, the definition for Sams scripts:
Full - Does a wipe of you data so you best have backups .gif)
Universal - is for "downgrading" - leaves the tz and gpt partitions alone flashes everything else (I believe it keeps data too, but didnt look at the script)
Keep - Keeps your data.
You will want to use Keep data in your case, I would imagine....
n00b
Posted 22 June 2014 - 12:50 PM
I think you need to regenerate your scripts based on the new FXZ files you extracted for KK
The script generator? Yeah, I have tried with fresh files, including regenerating scripts.
Tech Service & Beyond
Posted 22 June 2014 - 12:51 PM
No re-run the HouseOfMoto-ScriptGenerator.jar against the fxz files you downloaded and expanded for KK. then try again with HouseofMoto.bat
Tech Service & Beyond
Posted 22 June 2014 - 12:56 PM
I have a 926 not a 907. I can d/l the file to take a look....
n00b
Posted 22 June 2014 - 12:57 PM
No re-run the HouseOfMoto-ScriptGenerator.jar against the fxz files you downloaded and expanded for KK. then try again with HouseofMoto.bat
Yep, done that...several times, with fresh files.
Regarding type (full/Keep/Universal)...I have backups, and from what I heard, it seems many must do a FDR when OTA/FXZ to KK, so I'm fine with wiping.
Tech Service & Beyond
Posted 22 June 2014 - 01:05 PM
well, have you tried using the rsdgenerator and trying to do it vis RSD?
and then lastly maybe it is a moto-fastboot issue....from the error you have its definitely something with the system partition and space so may Baldy has it correct....
try the RSD way and I am d/l'ing the files
Tech Service & Beyond
Posted 22 June 2014 - 01:28 PM
Alright, I d/l'ed the 907 files and generated the scripts and it looks exactly the same as a 926. Now I am not sure whats up....I suppose its possible you need moto-fastboot
Matts last JB utility had it...at least its in my folders....but thats old, and not sure if there is something newer. If you have that you can try and rename the fastboot you have now to something else and rename moto-fastboot to fastboot and then re-run the script....
Tech Service & Beyond
Posted 22 June 2014 - 01:30 PM
And the system image you have is the same size as what I extracted so that looks ok too.
n00b
Posted 22 June 2014 - 01:36 PM
If you have that you can try and rename the fastboot you have now to something else and rename moto-fastboot to fastboot and then re-run the script...
Yeah, I already tried that, 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
Tech Service & Beyond
Posted 22 June 2014 - 01:42 PM
The variable not supported isnt anything to worry about, but I do not know Scotts...hmm...are you sure youre a Razr M xt907?!?!?!
Tech Service & Beyond
Posted 22 June 2014 - 01:44 PM
Scotts.....let start back at the beginning I'm a little wiped from riding.....
Are you using the original Moto USB cable, USB 2.0 port only and the correct drivers??
And yes the original cable does matter...
Also did you try the rsd method thats in Sams folders?
Tech Service & Beyond
Posted 22 June 2014 - 01:46 PM
where in LA you located? I'll meet you at a bar and fix you up for a beer
n00b
Posted 22 June 2014 - 02:24 PM
Thanks @cmh714...the RSD approach worked! Not certain why I had not tried that. I used the FASTBOOT approach for my previous JB FXZ, so would not have thought there to be an issue. If I lived in the LA area (I'm in DFW, TX), I would buy you a beer...thanks again to you and others herein. Now it's on to Towelroot!
I Void Warranties
Posted 22 June 2014 - 02:26 PM
Android Warrior
Posted 22 June 2014 - 06:06 PM
Non potest esse nisi unus
n00b
Posted 22 June 2014 - 07:06 PM
It was the fastboot binary.
Ok. For future reference...what needs to be edited/changed?
I Void Warranties
Posted 23 June 2014 - 02:46 AM
It was the fastboot binary.
Sent from my SM-P600 using Tapatalk
:
Android Warrior
Posted 23 June 2014 - 03:15 AM
My guess is if you have the platform tools fastboot in your path it may use that instead of the snapdragon support file I have people download. Of if you skipped installing that like half the people do, then it would use whatever's in the path. Whenever it says that system is too big, it's a good indication that the wrong fastboot executable is being used. Or a cable/usb port/driver issue.
Non potest esse nisi unus
Android Warrior
Posted 23 June 2014 - 03:16 AM
See what happens when you take some PTO... All hell breaks lose.
Sent from my VS980 4G
You should see my scary inbox. lol.
Non potest esse nisi unus
0 members, 8 guests, 0 anonymous users
This topic is locked
