Jump to content

[MOD] Dual Boot on the ZTE Skate [Updated - 09/08]


Recommended Posts

Guest razzmataz1478
Posted
I looked in boot folder, all that's in the zip is an updater script. Noting else. Not even a binary

Try again and when I moved the zip to the root of the SD card it worked.

Guest utternoob
Posted

I tried 5at. Will try again on H3 Blues using JB as the imaged rom

Guest razzmataz1478
Posted
Worked. Flash Loop Rom after creating gapps?

I think so but i got an assert boot image error when flashing.

Guest tilal6991
Posted

Yeah that's really not a surprise since you got a half baked debug release. Uninstall the apk I gave you, install the 4.1 apk and do the process again.

Guest utternoob
Posted

Just to be sure, is it loop rom then boot image or other way round. Tried boot image first and then rom but it didn't work

Guest timoti111
Posted (edited)

I cant get it to work. I am allways getting status 7 error in CWM. I do this:

1. CM7 and gapps on root of SD

2. In FusionXMultiBoot 4.2.0 I choose CM7 300mb system and 1000 data

3. Than Gapps

4. Than when I'am flashing Loop CM7 from multiboot folder i get Status 7 Error.

Edited by timoti111
Guest tilal6991
Posted

ROM then gapps then boot. All created with the 4.1 release.

I really need to write a guide for all this. That's my priority now lol. I've been putting it off for too long.

Guest tilal6991
Posted
I cant get it to work. I am allways getting status 7 error in CWM. I do this:

1. CM7 and gapps on root of SD

2. In FusionXMultiBoot 4.2.0 I choose CM7 300mb system and 1000 data

3. Than Gapps

4. Than when I'am flashing Loop CM7 from multiboot folder i get Status 7 Error.

No idea. I've never had a status 7. Don't use 4.2 though.

Guest timoti111
Posted

No idea. I've never had a status 7. Don't use 4.2 though.

Ok i will try 4.1.0

Guest utternoob
Posted

Hmm. Don't think gapps was created. Not sure why. What should gapps be called? I linked it to boot image for cfx 2. Create again?

Guest tilal6991
Posted

With 4.1 yes. As I've said 4.2 really was thrown out with a few changes which were only half do e.

Guest utternoob
Posted

Gapps created fine, installed ok, but then didn't boot, even after going through proper procedure

Guest razzmataz1478
Posted

What does "one of the images was not found" mean?

Guest tilal6991
Posted

You've mistyped either the system or data image in the finalisation tab.

Guest razzmataz1478
Posted
You've mistyped either the system or data image in the finalisation tab.

And if I want to use the nand data?

Guest tilal6991
Posted

You cant. Its just the way it is for now I'm afraid. It may change in a future version.

Guest razzmataz1478
Posted
You cant. Its just the way it is for now I'm afraid. It may change in a future version.

Right, I thought so. I've just created another loop ROM (cm7) and stuck at the splash...again.

Guest razzmataz1478
Posted (edited)

Recovery log: http://pastebin.com/Z2RXSWVR

Looks like there's no one home:

C:\Users\Ryan\android-sdk\platform-tools>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -

Edited by razzmataz1478
Guest Verhaaltjes
Posted

Really would like to try this one, as I jump ROMs regularly, but by the looks of it, it is still quite hard to get working. Has anyone else got it succesffully running?

Guest tilal6991
Posted
Recovery log: http://pastebin.com/Z2RXSWVR

Looks like there's no one home:

C:\Users\Ryan\android-sdk\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -[/code]

Log looks good. Try flashing the boot image in sdcard/multiboot/boot-images

If that still doesn't work post the boot.img of the created rom.

  • 1 month later...
Posted

Do the ROMs in the second post specifically have to go in either the SD card or nand? I was going to use H3 Blues on one and PA on the other so which should go on the nand and which on the SD please?

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.