Can't Update MZ608 to ICS

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
Hi guys,

I have an Bootloader unlocked MZ608 with 3.2.2.

Code:
0.268.4.MZ608.Retail.en.EU
1.6.0_268.4-MZ608
When I check for the update, I get 77.128.14.en.EU notification. I download it and say update. The system restarts and the update comes to a degree but then it fails showing up Android with exclamation mark.

I have downloaded Blur_Version.0.281.4.MZ608.Retail.en.EU and copied it to SD card. But I can not get into recovery mode to instal that too. When I try to get into recovery mode I get exclamation mark followed by a restart.

BTW, the device is MZ608 32 GB but it shows up in Motocast and device manager as MZ609.

What is the procedure that I should follow?

Thanks
 
Last edited:

potatorj

Member
Dec 22, 2011
12
0
0
Hi guys,

I have an Bootloader unlocked MZ608 with 3.2.2.

Code:
0.268.4.MZ608.Retail.en.EU
1.6.0_268.4-MZ608
When I check for the update, I get 77.128.14.en.EU notification. I download it and say update. The system restarts and the update comes to a degree but then it fails showing up Android with exclamation mark.

I have downloaded Blur_Version.0.281.4.MZ608.Retail.en.EU and copied it to SD card. But I can not get into recovery mode to instal that too. When I try to get into recovery mode I get exclamation mark followed by a restart.

BTW, the device is MZ608 32 GB but it shows up in Motocast and device manager as MZ609.

What is the procedure that I should follow?

Thanks
I think that this link can help you:
http://forum.xda-developers.com/showpost.php?p=33673095&postcount=673
 

HinotoriBR

Senior Member
Apr 2, 2011
287
74
0
43
São Paulo
I can't get into the recovery. I get an exclamation mark.

Thanks for the reply.
That wouldn't work as your Xoom 2 ME is not from Latin America and Motorola has different signatures for U.S., Europe and LATM...

What are you trying to do to get into recovery?

Have you tried to turn on usb debugging and using ADB to enter recovery? Just type adb reboot recovery and it should reboot into recovery, it will take a while, you should see a Green Android after about a minute, and then you can press VOL- and VOL+ to get the list of options... If that doesn't work, then it is likely that something is wrong/corrupt, I would recommend that you check if there is a SBF file for the Honey Comb distribution for your region and flash it using RSD Lite to restore everything back to stock... I know of at least two friends that had failed updtes due to corrupt files in /system (they did not pass the OTA check meaning that they are different from what is expected or they were deleted).

Also, you didn't try any of the recent hacks (safestrap/bootstrap recoveries), right? If you did, then I believe you would have to revert those hacks, or just flash the device back to factory condition using a SBF / RSD Lite, just remember to choose the right SBF file for your region, otherwise, device won't even boot.

Good luck
 
  • Like
Reactions: cool_recep

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
That wouldn't work as your Xoom 2 ME is not from Latin America and Motorola has different signatures for U.S., Europe and LATM...

What are you trying to do to get into recovery?

Have you tried to turn on usb debugging and using ADB to enter recovery? Just type adb reboot recovery and it should reboot into recovery, it will take a while, you should see a Green Android after about a minute, and then you can press VOL- and VOL+ to get the list of options... If that doesn't work, then it is likely that something is wrong/corrupt, I would recommend that you check if there is a SBF file for the Honey Comb distribution for your region and flash it using RSD Lite to restore everything back to stock... I know of at least two friends that had failed updtes due to corrupt files in /system (they did not pass the OTA check meaning that they are different from what is expected or they were deleted).

Also, you didn't try any of the recent hacks (safestrap/bootstrap recoveries), right? If you did, then I believe you would have to revert those hacks, or just flash the device back to factory condition using a SBF / RSD Lite, just remember to choose the right SBF file for your region, otherwise, device won't even boot.

Good luck
To get into recovery, I boot up the device with Vol + / - pressed. An dthen choose recovery and press vol +. The tab reboots and after about 2 minutes, I am in the middle of nowhere....reboot and the OS comes..


I have flashed SBF, that did not help either...

First I flashed the original:

1.6.0M-268.4-FLEMEM_UCATBLT1UMRTCOREEU_fastboot.xml.zip

then this one:

1.6.0M-281.8-FLEMEM_UCATBLT1UMRTCOREEU_fastboot.xml

I didn't try any hacks...

Now trying adb...

Update: That didn't work either. Same... 10 seconds of red M logo, 10 seconds black screen, 4 minutes android with exclamation mark and in the end restart into OS....

Thanks for the reply.
 
Last edited:

lambergio

Member
Mar 1, 2010
15
6
0
Hi guys,

I have an Bootloader unlocked MZ608 with 3.2.2.

Code:
0.268.4.MZ608.Retail.en.EU
1.6.0_268.4-MZ608
When I check for the update, I get 77.128.14.en.EU notification. I download it and say update. The system restarts and the update comes to a degree but then it fails showing up Android with exclamation mark.

I have downloaded Blur_Version.0.281.4.MZ608.Retail.en.EU and copied it to SD card. But I can not get into recovery mode to instal that too. When I try to get into recovery mode I get exclamation mark followed by a restart.

BTW, the device is MZ608 32 GB but it shows up in Motocast and device manager as MZ609.

What is the procedure that I should follow?

Thanks

I too was in your situation ... your device is the Xyboard mz609 to enter into recovery simultaneously press vol. on vol. down and power on, you will see a screen where you will have several choices ... with vol. down you move. with vol. on choose. if you see a triangle simultaneously press vol. up and vol. down and will go into recovery. with the device turned on you can use quick boot (from the market) to enter recovery and bootloader. when you enter bootloader you read unlocked? if it is unlocked you can have a custom recovery like me. thanks to runandhide05.
 
  • Like
Reactions: cool_recep

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
Holy! I am in recovery! Thanks man. Really appreciated!

I tried to install OTA ZIP via recovery but I got build.prop error. How to fix it?

It is something like that: (Modified some parts)

-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop ("/system/build.prop" , "ro.build.fingerprint") == "Motorola/RTCOREEU/fleming:3.2.2/1.6.0_281.4-MZ608/1328264683:user/release-keys"
file_getprop ("/system/build.prop" , "ro.build.fingerprint") == "Motorola/RTCOREEU/fleming:4.0.4/7.7.1-128-4_MZ608-14/1344529522:use/relase-keys"
E:Error in /tmp/sideload/package.zip
(Status 7)
restoring configuration START..
restoring configuration END..
Installation aborted.
 
Last edited:

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
OK. I am now downloading the honeycomb MZ609 fastboot.

Update: Flashed. The tab went into bootloop. Turned it off and went into recovery. Done wipe. Tried to flash OTA ZIP but gave signature verification error.

Update 2: Successfull reboot this time after wipe. I have noticed that baseband version says Unknown. Should I do something for that? I don't have a SIM to try.
 
Last edited:

lambergio

Member
Mar 1, 2010
15
6
0
OK. I am now downloading the honeycomb MZ609 fastboot.

Update: Flashed. The tab went into bootloop. Turned it off and went into recovery. Done wipe. Tried to flash OTA ZIP but gave signature verification error.

Update 2: Successfull reboot this time after wipe. I have noticed that baseband version says Unknown. Should I do something for that? I don't have a SIM to try.

I'm sorry, I forgot to tell you that you had to wipe. I also unknown baseband version and I imei-meid. I do not have microsim to try, but if you flash honeycomb mz608 imei again. I do not know why, but I prefer to have ics yet. when I find the files fastboot ics mz608 then I reflash.
 
Last edited:
  • Like
Reactions: cool_recep

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
I have found the version in build.prop:

1.6.0_281.4-MZ608

Flashed it with RSD. Now trying OTA again. Baseband is back BTW. Where is the IMEI writing?

Update: No luck with updating, again. Damn. Going to try recovery...

Update 2: Tried OTA Update. Got error:

assert failed: motorola.motoflash("/tmp/bp.img")
 
Last edited:

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
I'm sorry, I forgot to tell you that you had to wipe. I also unknown baseband version and I imei-meid. I do not have microsim to try, but if you flash honeycomb mz608 imei again. I do not know why, but I prefer to have ics yet. when I find the files fastboot ics mz608 then I reflash.
I think I should also wait for the offical fastboot files.

BTW, my friend have the exact tab with same specs that was successfully updated via OTA. Can I backup the ICS inside it and then install that backup to my tab via custom recovery?

Also another question: Can I flash MZ609 verizon fastboot? I will replace the radio IMG from Honeycomb fastboot in order to prevent baseband brick.

To sum up:

We have two tabs in hand. One was updated to ICS via OTA and works fine as below. But the other is resisting!

Can't update via OTA.
Can't update via Recovery.
And th worst, there is no Fastboot for MZ608 :)

Help me out guys, please :)

 

abaithad

Senior Member
Mar 31, 2010
66
19
0
Yes, you can flash the mz616 fastboot files, should work,
If it fails, you can always reflash honeycomb fastboot ones, but i think it will work.
Make sure you erase your user data at the end of process fastboot erase userdata

Sent from my XOOM 2 sing xda app-developers app
 

cool_recep

Senior Member
Aug 30, 2008
246
63
0
Istanbul
Flashed MZ616 via fastboot, totally bricked :) No charge, no screen, no bootloader... Nothing :)

Or maybe it is stuck in boot since when I connect the USB, I get a sound but the device is not recognized.
 
Last edited: