Database Info

Xoom 2, mz608 bricked

Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!

Semih91 said:
Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!
Click to expand...
Click to collapse
I hope that you are trying to flash the mz608 official fastbootfiles
I think I went wrong with the flash of the fastboot files.(do you have the latin america edition? -latem stands for latin america)
Otherwise you could probably have fixed it with pushing the original framework-res.apk.
I have the same model, if you need something, let me know.

Motorola mz608 bricked
Semih91 said:
Hey, guys
I've been lurking for a few days now, and decided to register and start a thread since I couldn't find any solution for my problem.
Anways, I'll start explaining.
I'm using a Xoom 2, mz608 running on Android 3.2.2. I've rooted my device and tried installing this: http://forum.xda-developers.com/showthread.php?t=1520476
After it tried rebooting, it ran into a bootloop. The motorola logo was animating, this was going on and on.
Then, I got into the recovery mode, since I couldn't unlock it. I selected wipe data/factory reset, "Yes, all user data". Tried rebooting failed again.
I've tried installing the MZ609 official fastboot files, it came to a stage where it seemed like it was installing it, however ended up with the android logo and a exclamation mark in it.
Then I tried installing this package: http://sbf.droid-developers.org/xoom2/list.php
That totally messed it up, now I'm getting these in fastboot:
Code:
AP Fastboot Flash Mode(S)(Boot Failure)
0A.8GB(sha-748ae9e-dirty, 2011-12-14 16:18:49)
eMMC Info: Size 16G
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG HAB(cg: mbr, status: 0x0056)
Now, I've lookup on other forums too, it seems many people are having this kind of issues.
Is there a way to solve this? Has anybody else that encountered this and managed to fix it?
Thanks in advance!
Click to expand...
Click to collapse
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...

mbuttenschoen said:
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...
Click to expand...
Click to collapse
If we would know the partition layout this could be possible.
i have one from belgium, so it could be the same model.
I don't know if the partition layout is the same as the 10".
The problem could be the fact that we have a locked bootloader

Hey guys, thanks for replying. I have a friend who also bought the tablet the same day and place I did. He's is still working. Do you think I could recovery it with his tablet? However, this european (Belgian) model, is locked and not able to be unlocked, so I think it's not possible..

mbuttenschoen said:
Hi folks,
I have exactly the same problem.
after installing the http://sbf.droid-developers.org/xoom2/list.php the tablet shows the error above.
Looking into the output of the console shows, that only the motoboot.bin - file could be installed, the other failed.
But this was the problem, I guess wrong version of the "motoboot.bin" - I read to late that it is the "latin American" one.
Does anybody know where to get the version of the file, that fits to the mz608 bought in germany?
a crate of beer (good german beer) for the correct file
one Idea: bying another one, and pulling the image: is it possible?
cheers
Michael
thanks for every answer...
Click to expand...
Click to collapse
BTW do you still have the output somewhere of the installation?
another thing we could try is:
wait for the update that will arrive in Q3, try to extract the files from there and try to fastboot flash them;

yelti said:
I hope that you are trying to flash the mz608 official fastbootfiles
I think I went wrong with the flash of the fastboot files.(do you have the latin america edition? -latem stands for latin america)
Otherwise you could probably have fixed it with pushing the original framework-res.apk.
I have the same model, if you need something, let me know.
Click to expand...
Click to collapse
Hi,
which ARE the official fastbootfiles?
I only found the files from sbf.droid-developers.org
and there, of course, i used the mz608 version.
cheers
Michael
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
yelti said:
BTW do you still have the output somewhere of the installation?
another thing we could try is:
wait for the update that will arrive in Q3, try to extract the files from there and try to fastboot flash them;
Click to expand...
Click to collapse
Hi,
yes, I have the output of running the "flash_fastboot.bat" at home, in the moment I'm at work.
But I remember: only the line "fastboot flash motoboot motoboot.bin" came back with "OK,
all other lines "verification error" or something else, I can write it down exactly this evening.
extracting the update is a good idea, too, if it comes... But Q3 is not ended yet
cheers
Michael

mbuttenschoen said:
Hi,
which ARE the official fastbootfiles?
I only found the files from sbf.droid-developers.org
and there, of course, i used the mz608 version.
cheers
Michael
---------- Post added at 02:32 PM ---------- Previous post was at 02:23 PM ----------
Hi,
yes, I have the output of running the "flash_fastboot.bat" at home, in the moment I'm at work.
But I remember: only the line "fastboot flash motoboot motoboot.bin" came back with "OK,
all other lines "verification error" or something else, I can write it down exactly this evening.
extracting the update is a good idea, too, if it comes... But Q3 is not ended yet
cheers
Michael
Click to expand...
Click to collapse
Its is hard to find the flash files, ik think we need emea instead of latam.
It think it would be possible to flash the hboot from a working model if you know which partition it is.

Semih91 said:
Hey guys, thanks for replying. I have a friend who also bought the tablet the same day and place I did. He's is still working. Do you think I could recovery it with his tablet? However, this european (Belgian) model, is locked and not able to be unlocked, so I think it's not possible..
Click to expand...
Click to collapse
I think i have something:
From ad shell dmesg > log.txt you can get the partition layout.
You have mbmloader mbm and mbmbackup.
One of these is the boot loader.
So try to dump these files and fast boot flash hboot hboot.img could work.
Dd if=/dev/mmcblkp0px of=/someplacewhereyoucanwrite/St.img
Could you provide me the system image somehow?
What does the "about" in system prefs says on the working device?
I bricked mine too unfortunately, but maybe I can get away with a system reflash.
Edit: corrected the partition name

a dmesg from my device
The partition layout
p1 (mbmloader)
p2 (mbm)
p3 (mbmbackup)
p4 (cdt.bin)
p5 (pds)
p6 (utags)
p7 (logo.bin)
p8 (sp)
p9 (devtree)
p10 (devtree_backup)
p11 (boot)
p12 (recovery)
p13 (cdrom)
p14 (misc)
p15 (cid)
p16 (kpanic)
p17 (system)
p18 (cache)
p19 (preinstall)
p20 (userdata)

yelti said:
a dmesg from my device
The partition layout
p1 (mbmloader)
p2 (mbm)
p3 (mbmbackup)
p4 (cdt.bin)
p5 (pds)
p6 (utags)
p7 (logo.bin)
p8 (sp)
p9 (devtree)
p10 (devtree_backup)
p11 (boot)
p12 (recovery)
p13 (cdrom)
p14 (misc)
p15 (cid)
p16 (kpanic)
p17 (system)
p18 (cache)
p19 (preinstall)
p20 (userdata)
Click to expand...
Click to collapse
Hi,
may be these partitions are there after booting.
in the 1.6.0M-272.12_MZ608_p2HW_BlurRegion02_CFC1FF_fastboot_signed_latam.xml fire it tried to flash these partitions:
fastboot flash boot boot_signed failed
fastboot flash motoboot motoboot.bin ok
fastboot reboot-bootloader
fastboot flash devtree devtree_signed failed
fastboot flash recovery recovery_signed failed
fastboot flash system system_signed failed
fastboot flash cdrom cdrom_signed failed
fastboot flash preinstall preinstall flashed
fastboot flash radio radio.img flashed
fastboot reboot
these are the files:
13.01.2012 22:29 8.388.608 boot_signed
13.01.2012 22:29 222.035.968 cdrom_signed
13.01.2012 22:30 524.288 devtree_signed
13.01.2012 22:34 2.622.464 motoboot.bin
13.01.2012 12:23 734.003.200 preinstall
13.01.2012 22:28 33.554.432 radio.img
13.01.2012 22:29 9.437.184 recovery_signed
13.01.2012 22:33 628.883.456 system_signed
maybe someone can find, which partition in the running device fits to "motoboot".
thanks
Michael

mbuttenschoen said:
Hi,
may be these partitions are there after booting.
in the 1.6.0M-272.12_MZ608_p2HW_BlurRegion02_CFC1FF_fastboot_signed_latam.xml fire it tried to flash these partitions:
fastboot flash boot boot_signed failed
fastboot flash motoboot motoboot.bin ok
fastboot reboot-bootloader
fastboot flash devtree devtree_signed failed
fastboot flash recovery recovery_signed failed
fastboot flash system system_signed failed
fastboot flash cdrom cdrom_signed failed
fastboot flash preinstall preinstall flashed
fastboot flash radio radio.img flashed
fastboot reboot
these are the files:
13.01.2012 22:29 8.388.608 boot_signed
13.01.2012 22:29 222.035.968 cdrom_signed
13.01.2012 22:30 524.288 devtree_signed
13.01.2012 22:34 2.622.464 motoboot.bin
13.01.2012 12:23 734.003.200 preinstall
13.01.2012 22:28 33.554.432 radio.img
13.01.2012 22:29 9.437.184 recovery_signed
13.01.2012 22:33 628.883.456 system_signed
maybe someone can find, which partition in the running device fits to "motoboot".
thanks
Michael
Click to expand...
Click to collapse
I see it has faild to flash the boot_signed.
Can you try to flash it manualy?
just put the boot_signed.img in your fastboor directory and fastboot flash boot boot_signed.img
See if that helps?
the motoboot can be only 2 partitions:
mbm or mbmloader.
I would thing mbmloader?

yelti said:
I see it has faild to flash the boot_signed.
Can you try to flash it manualy?
just put the boot_signed.img in your fastboor directory and fastboot flash boot boot_signed.img
See if that helps?
the motoboot can be only 2 partitions:
mbm or mbmloader.
I would thing mbmloader?
Click to expand...
Click to collapse
Hi,
i had first to wait that the battery is full, i cannot switch it off in fastboot mode, so it was empty after over last night.
now:
fastboot.exe flash boot boot_signed
sending 'boot' (8192 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.924s
anybody who can extract it from his mz608?
size and other files in my last posts
thankyou all.
cheers
Michael

mbuttenschoen said:
Hi,
i had first to wait that the battery is full, i cannot switch it off in fastboot mode, so it was empty after over last night.
now:
fastboot.exe flash boot boot_signed
sending 'boot' (8192 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.924s
anybody who can extract it from his mz608?
size and other files in my last posts
thankyou all.
cheers
Michael
Click to expand...
Click to collapse
I'm affraid that it won't work :crying:
We need a signed image to be able to flash.
I think a dump won't contain the sig, but I hope I'm wrong.
I think I have to send mine back to motorola
Do you have backlight bleeding at yours?
I have a spot where the light is bleeding from

yelti said:
I'm affraid that it won't work :crying:
We need a signed image to be able to flash.
I think a dump won't contain the sig, but I hope I'm wrong.
I think I have to send mine back to motorola
Do you have backlight bleeding at yours?
I have a spot where the light is bleeding from
Click to expand...
Click to collapse
Hi,
I've sent the Tablet to Motorola's Service, they have repaired it.
And - they didn't want to have any money
It has not yet arrived, but I have already a tracking number.
cheers
Michael

mbuttenschoen said:
Hi,
I've sent the Tablet to Motorola's Service, they have repaired it.
And - they didn't want to have any money
It has not yet arrived, but I have already a tracking number.
cheers
Michael
Click to expand...
Click to collapse
Nice they fixed m for free.
If you have him back, can you dump the system partition ( if it is still on Honycomb)
I would like to try to flash it to mine, if this fails, i'll return it too.

yelti said:
Nice they fixed m for free.
If you have him back, can you dump the system partition ( if it is still on Honycomb)
I would like to try to flash it to mine, if this fails, i'll return it too.
Click to expand...
Click to collapse
Hi,
it is still on 3.22 (3rd Q has not ended yet).
But: any idea how to do this without rooting?
Rooting (by using Root Method for Motorola Xoom 2/Xyboard Honeycomb By Dan Rosenberg) was the beginning of the desaster.
The rooting procedure was OK, but it was a 1-way-route.
Trying to flash back to stock (may be with the wrong tools/software/firmware) made the device unusable.
And I will not send it again to motorola's service, I think they wouldn't repair it again for nothing.
If you have an idea to read the system partition without rooting - I will do it, of course.
But how? reading may be possible, but there is no dd, no busybox without root.
So I think it will not work.
And, there is another point: I will sell the tablet and bye another one (Samsung P5100 I guess).
2 reasons: the display of the Xoom is ok, but: I think I am too old - a 10" device is a little bigger
And I want to have a tablet without a locked bootloader. Cyanogenmod 9 or 10 will be my friend, instead of waiting for Motorola.
I use CM9 on my little Samsung I9000 smartphone, and its OK. Much better than the stock 2.3.4. And it is available.
cheers
Michael

Without root I don't think it will be possible.
Unrooting is doable.
In Dan's script you can use the first 2 stages to make /system rw(I don't remember if I had to do a remount)
Then you can remove the Superuser.apk and busybox and your system is unrooted.
Next execute fase 3 and your back to stock.
If you don't want to do it, I understand.
Just let me know what you think, otherwise I will send mine back too.
mbuttenschoen said:
Hi,
it is still on 3.22 (3rd Q has not ended yet).
But: any idea how to do this without rooting?
Rooting (by using Root Method for Motorola Xoom 2/Xyboard Honeycomb By Dan Rosenberg) was the beginning of the desaster.
The rooting procedure was OK, but it was a 1-way-route.
Trying to flash back to stock (may be with the wrong tools/software/firmware) made the device unusable.
And I will not send it again to motorola's service, I think they wouldn't repair it again for nothing.
If you have an idea to read the system partition without rooting - I will do it, of course.
But how? reading may be possible, but there is no dd, no busybox without root.
So I think it will not work.
And, there is another point: I will sell the tablet and bye another one (Samsung P5100 I guess).
2 reasons: the display of the Xoom is ok, but: I think I am too old - a 10" device is a little bigger
And I want to have a tablet without a locked bootloader. Cyanogenmod 9 or 10 will be my friend, instead of waiting for Motorola.
I use CM9 on my little Samsung I9000 smartphone, and its OK. Much better than the stock 2.3.4. And it is available.
cheers
Michael
Click to expand...
Click to collapse

yelti said:
Without root I don't think it will be possible.
Unrooting is doable.
In Dan's script you can use the first 2 stages to make /system rw(I don't remember if I had to do a remount)
Then you can remove the Superuser.apk and busybox and your system is unrooted.
Next execute fase 3 and your back to stock.
If you don't want to do it, I understand.
Just let me know what you think, otherwise I will send mine back too.
Click to expand...
Click to collapse
Hi,
removing su and busybox I understand.
But what is this little programm "xyz phase x" doing?
where do you have this unrooting receipt from?
i am really afraid of ending in the same boot loop as before.
And I think, sending to service and waiting some days will be a good thing for you, too.
thank you, that you understand my situation.
cheers
Michael

mbuttenschoen said:
Hi,
removing su and busybox I understand.
But what is this little programm "xyz phase x" doing?
where do you have this unrooting receipt from?
i am really afraid of ending in the same boot loop as before.
And I think, sending to service and waiting some days will be a good thing for you, too.
thank you, that you understand my situation.
cheers
Michael
Click to expand...
Click to collapse
You didn't brick it by rooting it.
I think you bricked it when you changed the framework.apk.( I'm in the same situation )
Next you flashed the sbf which caused your bootloader problem.
The xyz finds a way to get a rootshell. Next it mounts the system RW and pushes the superuser.apk and busybox.
To unroot, it is the other way arround.
Maybe if you can mount your system rw, I think you can just remove the superuser.apk and execute busybox --uninstall.
With the next reboot you have your system back to read only.
You can find out how the xyz works in general by analysing the commands in run.bat.
Have fun with the samsung tablet.

[Q] [FIXED] HELP! Possible Brick on Xoom MZ607 WIFI

Hey! I need all your help, please. Yesterday, I saw that Motorola reveled a tool to unlock the bootloader of our tablet (I know, late). I read all the information about the process, and I could do this on my mz607 wifi. I downloaded all that I need, drivers and android sdk. After that, I rebooted the xoom on bootloader using adb command but....I can't do anything on this!!
I looked for some information about this, and I found in all forums that I can unlock bootloader with "fastboot oem unlock" command. It's false, I cant do nothing!! I rebooted my tablet and now, always run on bootloader and not boot system.
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
I found a germany forum with the same problem (I think) but I don't understand how they solved this.This the link
After this, I looked for other solutions and I found a tool of Motorola, RSDLite. I downloaded the correct file for my model, and when it flashing (7 step for the tool) not flash the boot.img! It's flash correctly other file packages (recovery.img, fastboot, etc) but it can't flash boot.img
Now, when I do "vol up+vol down+power" and select "Normal Boot", It doesn't do anything, the system would be missing!
I think it's can be a soft brick....or no, I dont know. I'm very worried about this and I would appreciate all your help.
Thanks. I'm waiting your answer.

Anybody can help me????

Ok, Anybody wants to help me!
Bye.

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Joshbone said:
This is my bootloader info:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6B (sha-h13f845, 2011-11-17 16:40:56)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.

runandhide05 said:
You may have tried to flash something before you said you did.
Basically your tablet wouldn't boot do to a failed flash, it said so right on the boot loader.
"AP Fastboot Flash Mode (S) (Flash Failure)"
Either way. You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Once you find them simple follow any tutorial on how to fast boot.
If you have trouble finding something just Google my name and you find a few helpful posts and topics.
And on the topic of unlocks. These will never and have not been unlocked. Furthermore a update (from Motorola) would have to update the bootloader for their new(ish) unlock tool.
Click to expand...
Click to collapse
So I have to find the same files for my MZ607? boot, recovery and system?

runandhide05 said:
You will have to find the fast boot files for your specific device! DO NOT THINK THEY ARE CLOSE ENOUGH it must be your device mz607!
Click to expand...
Click to collapse
Joshbone said:
So I have to find the same files for my MZ607? boot, recovery and system?
Click to expand...
Click to collapse

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Mjamocha said:
Click to expand...
Click to collapse
What??

Re: [Q] HELP! Possible Brick on Xoom MZ607 WIFI
Anybody more??

Joshbone said:
Anybody more??
Click to expand...
Click to collapse
Runandhide told you everything you need to know. You need to find the right regioned fastboot file for your mz607 and flash it. And that ypur bootloader is not unlockable. Any tutorial you were reading to unlock it would have to have been for the original xoom, not xoom2.

HELP! Possible Brick on Xoom MZ607 WIFI
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)

As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.

f5bud said:
Hello, I have the same problem,
I Bricked my MZ607 by flashing a bad "motoboot.img".
That and only that can be flashed!
Have you found a solution? I would also like to unlock the bootloader.
Thanks. I'm waiting your answer.
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:36:21)
eMMC Info: Size 16G
Device is LOCKED, Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (DG: system): Invalid SP Data
Invalid CG HAB (DG: system, status: 0x0056)
Invalid CG OTV (DG: system)
Click to expand...
Click to collapse
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you

Like the genius I am I've bricked mine too. It's a UK MZ607 that's been updated to JB from the US MZ609. I managed to delete the stock browser whilst trying to install a CyanogenMOD browser (long story) so figured I'd just repeat the steps that I used to flash the US MZ609 firmware. What I'd forgotten is that the first stage is to flash the US MZ609 ICS ROM then do an update to JB meaning I was effectively trying to downgrade. Everything flashes successfully except the boot partition which gives an error that it doesn't exist. Any ideas out there? I tried what I believe to be the original Fastboot file but no luck

Joshbone said:
Hi, my Xoom is the MZ607 WIFI model, and I fix whit this:
https://drive.google.com/folderview?id=0B5JuUC6auPR-bWJ2cFFUVVNmNFE&usp=sharing
Download the 3 files. First, install the Moto drivers, after that, execute the RSDLite and flash the zip.
Hope I've helped you
Click to expand...
Click to collapse
Also tried this and it fails when flashing the boot partition. I just ordered a factory cable to see if it can bring it back to life...

Is this zip still available?

alecbond said:
As I am not I Xoom 2 owner I can't help much.
However, Googling around found a few links that may be useful.
Possible stock files?
http://sbf.droid-developers.org/xoom2/list.php
Factory reset using hardware keys:
https://motorola-global-en-uk.custhelp.com/app/answers/detail/a_id/74653
And there's always:
http://www.xoomforums.com/forum/motorola-xoom-2-forum/
Hopefully this at least helps.
Good luck.
Click to expand...
Click to collapse
anybody who still has the mz607 files for a restore? The possible stock files link doesn't work any more...
http://sbf.droid-developers.org/xoom2/list.php

[Q] HELP! Need Modem for Photon Q 4G

Hey guys I have somewhat of a problem. I'm experienced when it comes to rooting phones (by no means an expert), but this problem has me stumped. You see, I was helping my friend to root his phone Photon XT897 and showing him how to do it. We got the device unlocked, installed CWM and rooted the device, all without issue. Anyways, I had to leave to go to work and he decided that he knew enough that he wanted to install TWRP recovery. According to him he did that by flashing an image of TWRP via fastboot, and everything was fine... except his wifi would no longer turn on. He then proceeded (and God alone knows why he thought this would help) but he formatted the modem in recovery and now, obviously he gets NO data connections whatsoever. I've scoured this site and everything I've been able to find online to fix this with no result; can somebody please help me? So what I need to know is this:
1. Has anyone else experienced wifi issues (i.e. the wifi no longer turning on) when flashing TWRP?
2. Is there any way to restore the modem?
3. Can I trade my friend in for a smarter version or at least store credit?
Thank you!!

No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here: http://sbf.droid-developers.org/asanti_c/list.php
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin

hfase said:
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here:
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
Click to expand...
Click to collapse
Thank you for the suggestion, but I tried both of those and neither one produced any results. I can't flash the NON-HLOS.bin in fastboot becuase it says:
F:\Scottys Droid ****\Devices\Motorola\Photon XT897\android-sdk-windows\platform
-tools>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'NON-HLOS.bin': No error
I can't flash the entire file with RSD because at first it throws the error:
getvar not found or something to that effect which I understand; getvar isn't a fastboot command. I then googled that problem and somebody with a similar issue with another phone said merely removing the line of code in the xml that calls for "getvar" fixed their problem. I tried that and now I get the error:
Flashing process failed flash sbl1 "sbl1.bin" -> phone returned fail.
Any other suggestions?

Are are the files extracted to folder you are running that command in?...
If not you will need to call the file with its absolute location. In ubuntu that looks like the following:
fastboot flash modem /home/hfase/Desktop/modem.bin
Hence the ". /" shown in my earlier example. Meaning "same dir" in linux. these will of course be different on Winblows.
If you cant get fastboot to flash just that try backing your system/data up with TWRP and just flash it with RSD. (using the edited XML found around here...) Basically for RSD to work you need to delete the getvar's in the XML.
If you look at my posts I posted a thread showing the XML file you need with the getvars edited so it works,, and even added the steps to relock the bootloader if you are interested lol
Sent from my XT897 using Tapatalk 2

Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?

arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
I'd love to... how?

arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
Actually, RSD Lite is suddenly working now... but I didn't do anything different so I don't understand why its cooperating. Well, there is one thing different that I did: I restored a TWRP backup that my friend made before the phone went down. You see, after he wiped the modem partition he installed a ROM (the Evervolve ROM), which didn't boot. He did this in an attempt to fix his mistake, thinking that the ROM carried a modem file in it. When I learned of this backup, I restored it and got into the phone; obviously the modem still wasn't working, but then I figured I would try the RSD flash again. So I removed the "getvar" lines of code from the "asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml" and it worked.
So the modem issue is now fixed, but wifi issue is not. I'm unclear as to whether I should close this thread because it's main issue has been solved, or if we can now take a look at the wifi issue. Basically, after flashing the TWRP recovery through Goo Manager that I downloaded from the market (I did this in the app by choosing the "install script" option, as I was instructed to by another of XDA''s threads) I then rebooted the phone only to find that the wifi didn't work. Whenever I go to turn the wifi on, the switch immediately goes back to the off position, but in the window below the switch it still says "turning on wifi." Please advise if I need to open a new thread, or if not, how we can perhaps solve this wifi problem. Thank you.

OK, glad you got the phone booting again.
Have you tried just doing a 'factory reset' in TWRP since you got the phone back to a functional state?
What kernel is flashed?

softbricked pixel

Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !

luigigigi said:
Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
Click to expand...
Click to collapse
Did you try turning the phone off and then using the power-on + volume down key to get to the bootloader menu? from there press the volume up key until you get to recovery and the press the power button. In recovery do a factory reset. That should take care of stuff. In future, don't use kingroot as it's a malware ridden app (that is if you care about your personal data). If you need root then use Magisk instead. Gives you root and also a root manager. If you are planning to tamper with root then make sure to have your bootloader unlocked. Let me know if factory reset worked.

yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.

luigigigi said:
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
Click to expand...
Click to collapse
I have one more idea you could try. Download latest OTA update from here: https://developers.google.com/android/ota
go into recovery and follow the instructions given on the link I just gave you and apply the update using adb sideload in recovery. (You have to manually get into recovery as you did before but follow the instructions from the point where you're inside the recovery.) This should work. Seems that kingroot/supersu corrupted your system somehow. Let me know if it worked.

i already came across that site because i was on android p, i didn't like it so i went back to nougat...anyway to say that i have the nougat image .zip , so do i have to download the latest firmware ?

ok ok, that's not the same...SORRY ?? !!

luigigigi said:
ok ok, that's not the same...SORRY ?? !!
Click to expand...
Click to collapse
yeah, it's not the same and you'll find the 8.1.0 update there and the updates from the past. Give it a go and tell me the results when you're done

i tried that, everything went as intended, when i power it up there's animations of 8.1 but still wont boot.
i tried to wipe data and boot again, nothing.
is there a way to flash stock rom with adb (just like we did with that update) ?

now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!

---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
luigigigi said:
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
Click to expand...
Click to collapse
It's the newer setup screen. Have you managed to boot into system. Is everything working?

Arju said:
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Click to expand...
Click to collapse
no since i did a wipe ( i guess i shouldn't have done that) , now when it boots it is locked, it is asking for a pattern, wjch i don't know because i didn't set a pettern previously.
i guess i'm stuck here for ever ? ??

is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !

((((Update))))
I didn't notice that there was a connect to Google option, so I finally set up the phone with my Google account and I'm back in.
I'm very thankful to you man you saved my phone, thank you a lot.
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )

luigigigi said:
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
Click to expand...
Click to collapse
I'm glad it worked itself out.
I'm from Norway. Married a swede so living in Sweden now. My parents are from Sri Lanka (the island below India) but moved to Norway before I was born. I've been to Sri Lanka once. Would like to travel to India sometime too :silly:
Algeria seems nice. Must be hot there. I've never been to Africa. Would like to travel there too some day

Yes totally, Algeria is really safe and people here won't bother you (like if you're wondering how u would be seen or received as a foreigner) there's foreigner all year round but especially in summer time, just have something planned in advance because it's Algeria not USA or another well developed country ? but still there's a lot to see here, definitely worth the visit.
When it comes to whether, well it's a Mediterranean weather so expect nice warm days, that being said, there's some time when it goes rainy with thunders and cold, for example now it is very pleasant outside, but yesterday the weather gone crazy... I guess that's because of the global warming.

luigigigi said:
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
Click to expand...
Click to collapse
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps

MpandAUS said:
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
Click to expand...
Click to collapse
I'm sure this gonna help me in the future, as i'm planing to try some custom Rom's and i'm probably gonna brick it again so ? ... Thanks you ? !

11.0.6.9 Completely broke system settings and services !

Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance

Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.

Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on

Kollachi said:
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Click to expand...
Click to collapse
Thanks but I can't do this, as i can't access system settings. Will it work with Oxygen updater app ?
EDIT: Oxygeon updater, also uses system settings...
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Thanks. Will try this if the above method doesn't work first.

Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)

Benfran said:
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Click to expand...
Click to collapse
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post

Qnorsten said:
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Click to expand...
Click to collapse
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks

Benfran said:
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Click to expand...
Click to collapse
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone

Qnorsten said:
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Click to expand...
Click to collapse
No luck.
I flashed all the .img and rebooted correctly. As before, everything works fine , except System settings (icon doesn't even appear). So i can't even check what version i have installed...
There was one issue flashing in fastboot though...only with 3 of the .img files :
reserve.img
xbl_config_lp5.img
xbl_lp5.img
With these 3 i got an error, the same one for all 3:
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Any idea as to why i'm getting this error and do you think this is related to the settings error ?
Thank you for all the help !

It finally worked !
I disabled the only magisk module i had active, and again flashed all the .img (still got the same 3 errors as above) and rebooted, and the system settings finally appear.... Although under a weird name.
The settings app is now called "Set data limit".
Also the characters of the clock app name are in Chinese now...
Besides these 2 things, the rest seems to be working fine now with 11.0.6.9
Thanks Qnorsten !