[XOOM 2] MZ616 32GB Australian Telstra branded Xoom 2 bricked?

[h4ck3rc1]

Hi all,
After using the Xoom 2 for a while as stock, and having experience rooting and installing custom ROMs to android phones I have, I decided to root my Xoom 2. I used Dan Rosenburg method and all was ok, got SU and installed Titanium backup and did full backup of system + user data. I know its always a good idea to backup
I have been on the lookout for a custom ROM for this device for a while but the bootloader is still locked and there is (to my knowledge) currently no way to unlock it, so that was out of the question.
After rooting and still having lag/performance issues, I decided to use ES File explorer in root mode to rename a few of Motorola's bloatware apps with the <insert bloatware app name>.apk and .odex to <insert bloatware app name>.apk.bak and .odex.bak.
I was following a list of apps that had been trial-removed by a developer and he had success. (I can't remember where I found the list).
All was still ok.
All these apps were in ~/system/apps by the way. I then renamed one starting with Moto, can't remember exactly, thinking it was bloatware, and the system crashes and now I am stuck in a boot loop and I can't access anything other than Fastboot Flash Mode, and even to get to there, I have to let it run dead flat, insert charger, wait for it to get to about 10%, then hold vol down key whilst pressing power. I have tried getting to recovery mode multiple times following instructions on motorola site, but each time it just gets stuck in boot loop.
Anyone got any ideas on how I could fix it?
I'm not really sure on how to use fastboot program on my PC, but when i enter "fastboot devices" in to command it just shows what looks to be a serial number. And "adb devices" returns a blank list, ie. not recognising anything plugged in.
Thanks in advance.

 

[Orkane1989]

Hold down both vol + and vol - then press and hold the power button. Should take you to recovery mode. Pressing vol - to scroll and vol + to select. May have to do a factory reset if you have accidently edited a system file. Re-root install TB and hopefully your back up is still there...

Edit: im also an aussie telstra branded mz616 and have had to do this before so it will work for you.
Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Thanks for the reply, what you said did help somewhat as I was able to get to to the boot menu. Problem is now, when I go to Recovery mode, it comes up with three following:
Invalid Flash Mode (S) (Boot Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:35:56)
eMMC Info: Size 32G

Device is LOCKED. Status Code: 0

Battery Low
Cannot Program
Connect USB
Data Cable

Invalid CG HAB (CG: mbr, status: 0X0056)

Any ideas?

Sent from my Sensation using xda app-developers app

 

[h4ck3rc1]

Also, I think it may be doing that because, before I found out how to bring up that menu (because the poor instructions I followed on the Motorola web site) I tried using fastboot mode to flash a recovery image I found on the internet and some commands in the batch file were successful but some failed.
If I didn't know any better, I think I may have bricked it.
I may be up for a new motherboard for it
: (

Sent from my Sensation using xda app-developers app

 

[Orkane1989]

Dont worry about the flash failure i have same thing from my noob days not realising i couldnt actually flash anything to it....

When you hold down all the buttons it should appear with a screen showing some info plus a menu with options to reboot normally, reboot in safe mode, wipe data and so on. Hit wipe data. And it will perform a factory reset.

Make sure you are hitting vol - vol + and then the power button last. Not all at the same time.
The screen you described is basically like download mode. Not the recovery screen.

Sent from my XOOM 2 using xda app-developers app

---------- Post added at 01:33 AM ---------- Previous post was at 01:28 AM ----------

If you manage to get to recovery and wiping everything doesn't work a new board is probably your best bet.

Tbh i would chuck the xoom 2 and put some cash towards a tab with flashing abilities. Or you could wait till at some point in the future for motorola to bring out a bootloader unlocking tool.

Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Ok, thanks heaps for your ongoing help. Which one of these options would be safe mode?
Screen says:
Boot Mode Selection Menu (0A.6C)
Vol Up Selects, Vol Down Scrolls
Available boot modes:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools

I tried going into a few of these and most of them end up leaving me on the Fastboot screen I described before. One of them, can't remember exactly, I think it was BP Only, leaves me with just the red Motorola logo and stays there.
I think I'm running out of options as the battery level its low and it doesn't seem to want to charge... : (
One last thought, its there a way I could reset/ wipe it using Fastboot, as that seems to be the only thing I can use...

Edit: The other thing it does other than Fastboot mode is comes up with a similar screen saying Invalid Flash Mode (S) (Boot failure) up the top... The rest of the screen looks like Fastboot mode

Sent from my Sensation using xda app-developers app

 

[h4ck3rc1]

Just a general question.... If I was to use Fastboot to erase all the partitions, in effect all I could access would be Fastboot and nothing else, correct? And if so, would I then be able to flash a new recovery.img file to then use? Or for that matter, a new system.img and boot.img and the rest? Or would the fact that the boot loader is locked interfere with that?
Once again, sorry about all the questions and thanks for the help.

Sent from my Sensation using xda app-developers app

 

[Orkane1989]

Im not a major flashing buff and my prominent knwledge sits with the sgs2 and ive only recently started researching into the xoom 2.
by the looks of it if normal booting and recovery (factory reset) do not work you have yourself a well bricked tablet. Im unsure about the image dump files being able to be flashed with a locked bootloader. I think it may be your last option and lets face it you dont have much to lose now hey?
As for the charging if your not using the charger that comes with the xoom you will experience very slow charge times. The charger that comes with it is optimized to produce a much higher voltage to charge the tablet within reasonable time... Using a standard usb charger you can face up to 10hrs before the device sits at 100%

Im unsure where you could find some stock image files but have a search around on xda maybe even post up what your looking for maybe someone will know exactly what problems you have and will be able to provide some more help.

But as i said, a locked bootloader leaves us xoom 2 users feeling rather left out with not muvh support when it comes to changing/flashing/fixing any part of the system firmware.

Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Yeah I'm pretty sure I've got a brick. I'll have to get the motherboard replaced I think.
Yeah I knew about the slow charging if using non genuine charger, but I left it overnight on the genuine charger that it came with, (the wall outlet only one) and still had low battery the next day.... I half expected that because I could only access Fastboot and nothing else and from what I can gather, the device won't charge in Fastboot so short of pulling the case apart and wiring the charger direct to the battery, it's bricked
I think I'll leave it to the professionals to fix.
Thanks heaps for all your help.

Sent from my Sensation using xda app-developers app

 

[Orkane1989]

Just had a quick search around and noticed that motorola have brung out a software tool to unlock bootloaders for their devices.
The mz616 is not yet supported as they are still updating and adding to their website.
But since the xoom 2 is the one device you can not manually unlock there would be great demand for it to be added to their list.
If you were able to unlock the bootloader you would have no problem at all flashing the stock firmware or third party rom to your device.
Have a search on google for motorola bootloader unlock tool and find the website. Keep updated with their changes and hopefully soon there will support for our devices.


If i find any other ideas i'll be sure to post them here for you. I know what its like to have a device that you have spent hundereds of dollars on and cant use it.

My little brother password locked my xoom and then could not remember it before i started becoming aware of flashing/rooting etc. And pretty much used my xoom as a large doorstopper for 3 months haha.
Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Thanks for that. While I am definitely looking forward to Moto releasing a unlock for it (if they decide to), I think the fact that I can't charge it is going to be the main issue now.
Hopefully it won't cost too much to fix

Sent from my Sensation using xda premium

 

[Orkane1989]

What are you doing to charge it? Are you using the charger that comes with the tab or a standard usb??

Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

I'm using the direct wall charger, (not the USB cord with charger attachment) so it should be getting full current charge. I left it overnight with it turned off (ie. black screen)

Sent from my Sensation using xda premium

 

[Orkane1989]

I'm using the direct wall charger, (not the USB cord with charger attachment) so it should be getting full current charge. I left it overnight with it turned off (ie. black screen)

Sent from my Sensation using xda premium

Hmmm does seem like you have truly bricked it. I would be sendind it in for repair. You may have to pay for it though because motorola will see you have tried flashing something over it which would void the warranty...

Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Yeah I rung them up and got the nearest repairer details and just told them what I had done. I figured they could tell that I had messed with it, considering it will only enter Fastboot LOL. I'll send it in and when it comes back, at least I'll know how to fix it if I stupidly brick it again haha.

Sent from my Sensation using xda premium

 

[Orkane1989]

Haha yeah oh well we learn from our mistakes. All good though sooner or later there will be a bootloader unlocking tool. There the android worl of flashing will be at our fingertips

Sent from my XOOM 2 using xda app-developers app

 

[h4ck3rc1]

Indeed, won't be soon enough. Thanks for your time and suggestions, appreciate it.

Sent from my Sensation using xda premium

 

[Orkane1989]

Indeed, won't be soon enough. Thanks for your time and suggestions, appreciate it.

Sent from my Sensation using xda premium

No worries. Thought ide give as much info as possible cause there isnt that much support for the mz616, especially Australian carrier locked devices.

Sent from my XOOM 2 using xda app-developers app

 

[canyonrunner]

The fastboot files are avail now for the Australian xoom 2....do a search for it and you will be able to get it running again....

 

[kent_lkc]

Thanks for that. While I am definitely looking forward to Moto releasing a unlock for it (if they decide to), I think the fact that I can't charge it is going to be the main issue now.
Hopefully it won't cost too much to fix

Sent from my Sensation using xda premium

You don't need charger ... all you need is Factory Cable. See pic below:-

Self made Motorola Factory Cable.
1. Use Motorola Stock USB Cable
2. Jumper Pin 1 to Pin 4