Database Info

[Q] New user - German Xoom in DK (MZ604) no ICS update

Hi everybody
Returned my Prime because of a lot of reasons and now I've ended up with a Xoom
This is my first tablet.
But why cant I see/recieve the ICS update?
I chose Danish as language, is that the reason?
Model: MZ604
Android-Version: 3.2
Tell me what u need to know, or what I have to do
Thx

is it a bad thing to make it a GED device? Got the guide ready.
Im using it in Denmark. Does that mean anything? Im not going for custom roms rigth now. Maybe later
Plz answer!
----
AND will I have access to the Danish Android Marked or only the US-version?

kunddizzle said:
Hi everybody
Click to expand...
Click to collapse
Hi
kunddizzle said:
But why cant I see/recieve the ICS update?
Click to expand...
Click to collapse
'cause there just is no ICS update for any xoom that supports more than wifi
forget what I said. I kind of read MZ601... Clearly, your model is a Wifi-only-xoom. I am not sure though if this (the european) version should already have received the ICS upgrade. Some sources I found state that it will be released in Q2/2012... However, another pointer I found was: are you positive your xoom is not unlocked (/are you the first to own it)?
kunddizzle said:
I chose Danish as language, is that the reason?
Click to expand...
Click to collapse
no
kunddizzle said:
Tell me what u need to know, or what I have to do
Click to expand...
Click to collapse
just unlock and go with a custom rom
kunddizzle said:
is it a bad thing to make it a GED device? Got the guide ready.
Click to expand...
Click to collapse
what is a GED device? Which guide?
kunddizzle said:
Im using it in Denmark. Does that mean anything?
Click to expand...
Click to collapse
uhm, not really
kunddizzle said:
Im not going for custom roms rigth now. Maybe later
Click to expand...
Click to collapse
"later" is right now, right? No? How about now?
kunddizzle said:
AND will I have access to the Danish Android Marked or only the US-version?
Click to expand...
Click to collapse
what's the difference? Why would you get "the US-version" with a german xoom?

GED means its a US version and Google Dev device...
How can I check to see if its unlocked or not?
And will it not update if unlocked?
And yes I bought it as 2nd hand.. but it was almost not used..

kunddizzle said:
GED means its a US version and Google Dev device...
Click to expand...
Click to collapse
ahh, Google Experience Device, now I got it
kunddizzle said:
How can I check to see if its unlocked or not?
Click to expand...
Click to collapse
if you have fastboot set up on your computer reboot your xoom into bootloader mode (for example by entering adb reboot bootloader in a windows terminal, after all, if fastboot has been set up, adb is most likely also set up; USB debugging must be turned on in android settings for this) and once the xoom rebooted into bootloader mode just enter fastboot getvar all, that should return something like
Code:
...
(bootloader) battery-status: 61%:7.671V:0.9844A:21.75C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
all: Done
finished. total time: 0.547s
unlocked will be yes if the device is unlocked and no if it isn't; iswarrantyvoid will be yes if the device has ever been unlocked.
kunddizzle said:
And will it not update if unlocked?
Click to expand...
Click to collapse
that is correct. You can re-lock your bootloader if it isn't locked, but you need to have stock everything for that to work (/system /recovery /boot)

Trackid worked which i read meant it was locked

there you go.
Not unlocked!

Why do you prefer stock rom? The custom roms work great. If you want a rom that is very close to stock I'd recommend TeamEOS 1.0.

I dont say I dont want a custom ROM soon, but I would like to try the official ICS first.
And I cant figure out why I dont recieve the OTA update? Is some of my infos wrong regarding the screenshots I've posted?

decided to go the custom room way..
but need some help!
What to do after I have unlocked the bootloader?
I've downloaded Eos wingray and the eos Gapps.
Havent done this before

Did you install ClockworkMod recovery? If so:
-place the EOS rom and Gapps on the external SD card
-make a backup of your stock rom
-do a wipe/factory reset
-flash the EOS rom
-flash the Gapps
-reboot your Xoom

kunddizzle said:
What to do after I have unlocked the bootloader
Click to expand...
Click to collapse
after you unlocked your bootloader you have to flash a custom recovery (I recommend the recovery linked in this thread), then boot into the recovery and flash the custom roms .zip and the gapps.zip. To do all that, you can just follow the instructions in that thread, just don't flash the xoom-root.zip, instead flash the team EOS-zip and the gapps.zip
If I was you, I'd make a nandroid backup right after booting into recovery for the first time, you could use that backup to restore to stock later on, if you like. This will even overwrite your custom recovery once you boot it, after that you can lock your xoom again.
tl;dr
put roms zip-file(s) onto SD-Card
unlock bootloader
flash recovery
boot recovery
(optional) Backup everything
flash the roms zip-file(s)

I decided to test the US GED ROM first.
Then I have something to compare with!
Thx for the guide. Will use it soon!
If I want to download the german or european version, can I use those listed here?:
http://developer.motorola.com/products/software/
---
Im downloading the US updates from 3.0 and OMW to 4.0.3
It seems that I didnt even have 3.2.1 ? So is something was wrong?? It only showed 3.2

[Q] Current Recommened Bootloader version?

I just got done using Flatline (http://forum.xda-developers.com/showthread.php?t=2455925) to generate my nvflash blobs (yay!!). The process for Flatline has you install a modded bootloader and custom recovery to generate the nvflash blobs, as I unstand it. With that completed, I was looking to reinstall a standard bootloader and custom recovery.
I managed to get fastboot to cooperate and install CWM Touch 6.0.4.4, but I haven't been able to get fastboot to load the "us_bootloaderblob" file for the 10.6.1.14.4 bootloader. The page for the bootloader (http://forum.xda-developers.com/showpost.php?p=40623406&postcount=1997) has links to 4 files - 2 zip files that can be flashed via recovery, and 2 other files to be installed via fastboot. Unfortunately the file linked to for the US version of the zip files is no longer available, but the fastboot file for the US version is, so I've been trying to reinstall it that way without much success. The tablet connects via fastboot ("fastboot devices" reports a device present), but issuing the command (copied and pasted from the page) seems to attempted to send the file to "staging" but does not respond after that. I've waited a good 10 to 15 minutes without the command finishing.
I could dig more into whether I have the right drivers installed, although all the commands through the flatline process worked just fine, but I think I'd rather try just flashing a zip file through CWM recovery.
So the big question: Where can I find a bootloader zip file to flash? Also, which bootloader is now recommended? I had 10.6.1.14.4 installed shortly after dasunsrule32 posted it, but I've seen references to 10.6.1.14.8 and 10.6.1.14.10. Do the newer bootloaders fix or improve anything?
Any help is greatly appreciated!!

montec77 said:
Also, which bootloader is now recommended? I had 10.6.1.14.4 installed shortly after dasunsrule32 posted it, but I've seen references to 10.6.1.14.8 and 10.6.1.14.10. Do the newer bootloaders fix or improve anything?
Click to expand...
Click to collapse
No, they only change the version number (I compared the binaries). So any bootloader from 10.6.1.14.4 to 10.6.1.14.10 is fine for all current ROMs.

_that said:
No, they only change the version number (I compared the binaries). So any bootloader from 10.6.1.14.4 to 10.6.1.14.10 is fine for all current ROMs.
Click to expand...
Click to collapse
Any chance you have a bootloader zipped up that I can flash in CWM or a link where I can download it? :fingers-crossed:

montec77 said:
Any chance you have a bootloader zipped up that I can flash in CWM or a link where I can download it? :fingers-crossed:
Click to expand...
Click to collapse
Forgive my asking, but you do have the bootloaderblob file in the same directory as your fastboot.exe, right?
I don't know where you can get the bootloader only, but here's a link where you can get a flashable bootloader/TWRP package. If you're willing to try TWRP download it from the OP.
http://forum.xda-developers.com/showthread.php?t=2425383

berndblb said:
Forgive my asking, but you do have the bootloaderblob file in the same directory as your fastboot.exe, right?
I don't know where you can get the bootloader only, but here's a link where you can get a flashable bootloader/TWRP package. If you're willing to try TWRP download it from the OP.
http://forum.xda-developers.com/showthread.php?t=2425383
Click to expand...
Click to collapse
Yes -- the bootloaderblob is in the same directory. It could be that I'm just not giving it enough time to write before I give up on it, but I've given it upwards of 15 minutes or so without the command finishing.
I tried using one of the flashable bootloader/TWRP packages, and flashing it fails, too, with:
"asset failed: write_raw_image("/data/media/blob", "staging")"
It's as if it won't let anything be written to staging.
I'm going to ask this in the Flatline thread, but I do thank you for your reply!!
*UPDATE* I guess I'm not going to post this in the Flatline thread because I'm not allowed to post in Dev threads -- haha... oh well.
Has anyone who's gone through the Flatline procedure for extracting nvflash blobs followed up and returned back to a stock bootloader? Neither fastboot nor flashing a package in recovery seem to want to write to staging for some reason. I read in another thread that it might be because the bootloader isn't unlocked (double-negative, I know..). Upon booting, the tablet says the bootloader is unlocked in the upper-left corner, but issuing "fastboot -i 0x0b05 getvar all" returns:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
(I've replaced my serial number with x's) Is it normal for this command to report back that the bootloader not unlocked, or is that bit of information referring to something else?

montec77 said:
Is it normal for this command to report back that the bootloader not unlocked, or is that bit of information referring to something else?
Click to expand...
Click to collapse
IIRC this is normal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

_that said:
IIRC this is normal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
That's a relief that's it's still unlocked (not that it was behaving like it was locked again).
Another thought -- could my problem be that the staging partition is not mounted in fastboot since it didn't show up in the list of partitions from my previous post? After all, the bootloaderblob is supposed to get written to staging, so if it's not there, maybe that's why it's getting stuck..?

montec77 said:
That's a relief that's it's still unlocked (not that it was behaving like it was locked again).
Another thought -- could my problem be that the staging partition is not mounted in fastboot since it didn't show up in the list of partitions from my previous post? After all, the bootloaderblob is supposed to get written to staging, so if it's not there, maybe that's why it's getting stuck..?
Click to expand...
Click to collapse
I'm no expert on this, but I seriously doubt it. There's a bunch of partitions on this device and they aren't listed either.
I wonder if you might have better luck with TWRP instead of CWM. Why don't you try to fastboot TWRP 2.6.1 to your tablet and try to flash the BL/TWRP package from the CROMi-X thread again?

berndblb said:
I'm no expert on this, but I seriously doubt it. There's a bunch of partitions on this device and they aren't listed either.
I wonder if you might have better luck with TWRP instead of CWM. Why don't you try to fastboot TWRP 2.6.1 to your tablet and try to flash the BL/TWRP package from the CROMi-X thread again?
Click to expand...
Click to collapse
Happy Happy Happy
That did the trick! Just about the only combination I probably hadn't over the last week or so.
I flashed the TF700-specific TWRP 2.6.3.1 (without the bootloader in it) found in this post: http://forum.xda-developers.com/showpost.php?p=47153833&postcount=488&nocache=1&z=3454984016028628 , which finally allowed me to flash the bootloader/recovery package in the OP of the CROMi-X thread. Every time I had tried to flash the same bootloader/recovery package within CWM 6.0.4.4 it would fail at trying to update the bootloader, so neither the bootloader nor TWRP recovery were getting installed.
Expert or not, I can't thank you enough for your help, berndblb!! :highfive:
A follow up question for those in-the-know: So the custom recovery that I was using (CWM 6.0.4.4) was stopping flashing a new bootloader to staging through fastboot, or was that just a coincidence? I'm not going to try to fastboot the bootloader again to test it -- I'm on 10.6.1.14.10 US and I'm happy to leave it alone until I *have* to update it again.
The reason I'm asking it to try to better understand the purposes and relationship between APX, Fastboot, recovery. By all means, someone please correct me where I go wrong with this since I'm just speculating:
APX is a very low-level interface, maybe comparable to the BIOS in a PC, where as long as the hardware isn't damaged or corrupted, this interface will be available to read and write (primarily) to memory locations in the internal sdcard?
Fastboot is one level up, providing a fairly low-level interface, with more options for dealing with partitions created on the sdcard?
The recovery (as in CWM or TWRP, etc) is another level up, providing an user interface on the device to install packages and deal with system-level stuff before Android actually boots up and takes over?
I don't even know if any of that is even close to correct, but following teh above, that's why I would be surprised and why I'm asking if the custom recovery would have been able to stop fastboot from installing the bootloaderblob -- I would have thought that the custom recovery would not have been started yet while in fastboot mode.

I am glad this did the trick for you! :GOOD:
I can't tell you why CWM didn't work - I just have no experience with it.... My guess: The bootloader/recovery combo does not work....
About APX, fastboot etc. you're pretty much dead on. Except that APX mode is useless to you if you didn't generate the NVflash blobs to use in APX BEFORE you actually need them.
If you want to make your tablet brickproof, check out this guide from the good people at AndroidRoot who gave us the option of flashing away with peace of mind: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash/
Note: This requires you to flash a customized bootloader and recovery! You can fastboot back to your current setup afterwards, but maybe you want to give yourself a week or so to just enjoy what you just obtained
Read the guide very carefully and check out the corresponding thread on XDA. This is not for the faint of heart, but I made it work - so it's not that hard
Re-reading your post, there's maybe a little more info I can provide. When you flash a bootloader, it actually gets written to the staging partition. During the next boot it will be written to it's proper partition. That's why you cannot flash a bootloader in recovery and in the same session flash a rom. You have to boot in between for the bootloader flash to take hold.

Already have my multiple copies of my nvflash blobs stashed safely away, and yes, all thanks to the amazing work by the guys at AndroidRoot! I had been kicking myself for just about a year because the first thing I did after I got the tablet was to install any Asus system updates to see if I could live with the tablet stock. Little did I know Asus had *just* pushed the 9.4.5.30 bootloader which blocked access to the nvflash blobs (yeah, and that was the first thing I installed within the first 15 minutes of owning it!! D'oh..).
The Flatline procedure worked great, and exactly as described on the AndroidRoot site and in the Flatline thread. After I had the blobs, I wanted to restore CWM and a standard bootloader. I managed to get CWM installed first, and, well,.. got stuck trying to reinstall the bootloader.
I understood how the bootloader was supposed to get installed -- I've been avidly lurking through the forum for quite a while. But I could not for the life of me get anything to actually transfer it to staging. Apparently the culprit was CWM -- installation would just fail. Perhaps this is a heads up for anyone else using CWM Recovery if we have to update the bootloader again?
Again though, many thanks for your help!!
PS. New Golden Rule: **NEVER** install a manufacturer's system update until you've read all the relevant XDA posts about what is does and what it blocks!! (I stupidly lost root on a Droid 2 Global for about 3 or 4 months that way -- seriously considered getting rid of the phone until someone found away to get root back and I could start flashing roms again!.)

[Q] something like CMInstaller for my TF700?

Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.

I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.

CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.

madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html

Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.

madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP

Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!

madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.

What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:

LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?

berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:

LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend

berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...

berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.

Looking for advice

Hello People of XDA,
I am wanting some advice for my tablet (TF300t). I want to make an NV backup and duel boot this device with Ubuntu or Arch. I have already unlocked the bootloader and I was looking at backing up my NV Items. To add I have not installed any recovery I was looking at TWRP as it seems to be more stable on the Transformer than CWM. I am currently running10.6.1.8 firmware ( I bought it with this pre-installed) and androidroot.mobi says it requires 10.6.1.15.3 I have downloaded this version of the rom and unzipped put it on the flash and went to the settings and tried to update but its failed a few times and I have also downloaded it a couple of times. Also I was wondering about the boot loader and 3rd party roms. I have been reading but this device is a little harder for me to understand due to the complicated nature of what I want out of it.
Thanks for reading and any advice.

Trigger911 said:
Hello People of XDA,
I am wanting some advice for my tablet (TF300t). I want to make an NV backup and duel boot this device with Ubuntu or Arch. I have already unlocked the bootloader and I was looking at backing up my NV Items. To add I have not installed any recovery I was looking at TWRP as it seems to be more stable on the Transformer than CWM. I am currently running10.6.1.8 firmware ( I bought it with this pre-installed) and androidroot.mobi says it requires 10.6.1.15.3 I have downloaded this version of the rom and unzipped put it on the flash and went to the settings and tried to update but its failed a few times and I have also downloaded it a couple of times. Also I was wondering about the boot loader and 3rd party roms. I have been reading but this device is a little harder for me to understand due to the complicated nature of what I want out of it.
Thanks for reading and any advice.
Click to expand...
Click to collapse
As you are upgrading, I suggest to use the latest version 10.6.1.27.5. It works fine for the nvflash tools. Though there seem to be little (or no?) changes between bootloaders 10.6.1.15.3 and 10.6.1.27.5, the latest version is what most ROM developers use for development and testing.
When you unzip the Asus ROM twice, you find a file named "blob". Flash that using fastboot:
fastboot flash system blob
For more detailed instructions, check the sticky guides in the general section.
Sent from my TF300T using Tapatalk

Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
f69m said:
As you are upgrading, I suggest to use the latest version 10.6.1.27.5. It works fine for the nvflash tools. Though there seem to be little (or no?) changes between bootloaders 10.6.1.15.3 and 10.6.1.27.5, the latest version is what most ROM developers use for development and testing.
When you unzip the Asus ROM twice, you find a file named "blob". Flash that using fastboot:
fastboot flash system blob
For more detailed instructions, check the sticky guides in the general section.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse

Trigger911 said:
Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
Click to expand...
Click to collapse
Never used that OTA mechanism myself. Using fastboot or flashing the ZIP (unzipped once) using recovery seems so much more natural to me.
For dual-boot have a look at my MultiROM thread, though Linux support is not there yet.
Sent from my TF300T using Tapatalk

Trigger911 said:
Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
Click to expand...
Click to collapse
No I don't recommend using the built in one due to electrical infetterence. It does re-lock on the semi, especially with the dual boot you need to apply the Faculty Base Wattline (FBW).
Here is how I did mine custom, i can post more pictures if you want:
s7.postimg[_DOT_]org/ubm43p7pn/353535jpg[DOT_]jpg[/url]

I am going use the blob to update I will try to post back what I figure out

OK I got it all working the flatline.img will put the bootloader to what it needs to work and I installed twrp and omnirom seems to run a little smoother still reading up about the linux porting tho.

[Q&A] [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926

Q&A for [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Is this the ROM for the XT926 from Dhacker? Sorry for a noob type question, but sometimes the ROMS have 926 in the file name which makes it easier for guys like me to know I am getting the right one.
androidhosting.org/Devs/Dhacker29/cm-11-20140207-UNOFFICIAL-vanquish.zip

Poor call quality
Has anyone else had the issue where there is poor audio quality in the earpiece? The audio is all crackly and fuzzy, and makes it very hard to understand. I'm not sure if it's hardware or software related right now, and am trying to find out. Another issue which I've had for the past couple months is that the maximum speakerphone volume is SUPER low, much lower than equivalent speaker volume for a youtube video or something. Might this be related (for example, the earpiece volume, which can now go to a deafeningly high level is actually using the gain meant for the speaker and vice versa (resulting in clipping of the signal going to the earpiece, and poor quality)?

Stuck in a boot loop between Motorola boot animation and CWM Recovery menu
Hi guys, Im looking for some help.
I'm a Razr HD (XT925) owner, unlocked bootloader, rooted and CWM 6.0.4.4.
I was running the latest CM 11 KK4.4.2 nightly. Lately it was a bit unstable (freezing and rebooting...sometimes stuck into the CM animation). Due to that I decided to give Epinter's [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926 a try.
Everything ran smoothly, without any sort of error but after the reboot, it got stuck into a loop between the Motorola boot animation, which keeps on my screen for approximately 30 secs, after that the screen turns black, the same Motorola boot animation pops up again, this time for a bit short time and finally, it brings me to the CWM Recovery menu.
I've tried to restore my CM11 KK4.4.2 image but it quickly shows me a message saying
"Checking MD5 sums...
MD5 Mismatch!"
Another strange facts:
After performing the wipe data/factory reset there are the following messages:
(Please note that Bold/Italic ones seemed sorta strange for me...maybe just because I'm being a noob though!)
"__Wiping data...
Formatting /data...
Formatting /cache...
Formatting /SD-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard.android_secure"
Data wipe complete"
E:unknown volume for path [/sd-exit]
MD5 checksum mismatch"
While trying to wipe Delvik cache the following message pops up:
"E:unknown volume for path [/sd-ext]"
So, atm, as you can imagine, my cell phone is sorta useless!
Can anyone help me?!?
Thank you in advance for your time and attention!
Cheers!
Edit 1: I've performed Wipe data/Factory reset, Wipe cache partition and Wipe Delvik cache before applying the Epinter's .zip and ggapps from my SD card. I did the same right before Epinter's .zip and ggapps both got installed without any sort of error message. I've did the same several times after the problem starts as well. In my last attempt of solving it by myself, I've repeated it all again since the the 1st step...all wipes and reinstalling both Epinter's and ggapps!
Edit 2:
I've managed to install from CWM an old .zip I found on my storage and my cell phone came back to life in the very same state it was!
Now, I was reviewing each step in order to try to install Epinter's CM11 KK4.4.4 and I've seen he wrote the following:
Recent versions (July/2014) requires an updated (KitKat) bootloader
After that, a doubt came to my mind...Could it be the cause of this mess I was stuck into? Is my unlocked bootloader JB or KK? How can I know it?!? If it is JB, how can I change it to KK?

If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl instead epinter's old builds

Thanks and a heads up
DorianX said:
If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: (Ive had to delete the link because of my low number of posts) instead epinter's old builds
Click to expand...
Click to collapse
Thanks a lot bro!
Well, in this case I'm pretty sure I'm running a JBBL then!
Believe it or not, after several wipe data/cache it is running...with some freeze outs and restartings more often than Id like but still...its running!
The link for the latest JBBL build is kinda broken (After choosing the latest build, it brings me to a 404 not found error page).
Thanks again and Ill come back in a few days when the link to the latest JBBL is working! As for the compatible GAAPS for the latest JBBL build...the same one Ive used alongside with Epinter's should be ok?!?
Cheers!

Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
http://forum.xda-developers.com/showthread.php?t=2779598
Or here:
http://forum.xda-developers.com/showthread.php?t=2397942

Thanks again and...
DorianX said:
Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
(Links not allowed yet for me)
Or here:
(Links not allowed yet for me)
Click to expand...
Click to collapse
Thanks again!
Taking as true the assumption that from now on the vast majority of ROMs to come will be made to be used on KKBL, wouldn't it be worth to upgrade to a KKBL now? Would it be too complicated since I'm not sure what was my default cell phone OS since I'm the 2nd owner and I've bought it from an ebay like site here at Brazil! Any tutorial links?
Cheers again!

What is gcm services and is it safe to force close it? It's eating my battery.

[XT925] Stock ROM with KK BL to install CM11
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!

cristian04 said:
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!
Click to expand...
Click to collapse
As it has been widely discussed multiple times on multiple threads on all the msm8960 device pages, if your device has not been given the official Moto Kitkat, or if you have not taken the official Moto kitkat update, you will use the moto_msm8960_jbbl builds. If your device has been updated to the official Moto Kitkat, you will use the moto_msm8960 builds.
All bootloaders come from Moto, not CM or another third party ROM developer, so no it is not possible to upgrade or downgrade your bootloader with a custom ROM. You can only do this using the sbfs and the guides here on xda.
Sent from my ATRIX HD using XDA Free mobile app

Camera not initialise
Hey i tried the copy/paste method( placing the files in system/app), But then i'm getting the error "Camera not initialize". Can anybody help me, it will be Thankful...

As of late I'm experiencing problems with the Wifi tethering dropping my service. I've been running CM11 for awhile now with no major issues until recently
The problem I'm having is once I enable wifi tethering, hotspot becomes active and all is well. As soon as I connect a device to that network, my phone drops service. This will happen repeatedly. Every once in awhile the service will hold but it's only a matter of time before it drops again. This problem gradually became worse over time until it happens everytime.
Anyone experiencing this issue? I was hoping it was an issue with my current 20140609-SNAPSHOT but I just updated to cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl and still receiving the same problems.

expired link
Hi
it seems the download link for epinter roms is temporary (hope so) dead
"This Domain Name Has Expired"
But I do no read this thread very often; may be I have did'nt read something about this fact
Kind regards,
Serge

Kbbl problem
Dear developer i own two razr hd's (xt925) both currently running stock kitkat uk build ota.when i install any kkbl rom i get E: Error executing updater binary in zip '/external_SD/roms/cm-11-20141008-SNAPSHOT-M11-moto_msm8960.zip'.
I have tried 6 of your builds and some pa too on both devices I have also tried it on twrp 2.8.1.0,2.8.0.0,2.7.0.0 and Phil adv cwm,cwm 6.0.3? . The problem is probably something wrong with my razr hd but I really need to know what it is . Please could you help PS I have downgraded to jb and the jbbl is working fine but a bit slow sometimes.(EDIT)
Fixed by editing update script. Changed ro.boot.secure_hardware from 1 to 0

Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.

Wizard1Canada said:
Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.
Click to expand...
Click to collapse
Boot into fastboot and type "fastboot getvar all" we need more info to help
Sent from my ATRIX HD using Tapatalk
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
http://www.android.gs/install-twrp-recovery-on-motorola-razr-hd-xt925/
Sent from my ATRIX HD using Tapatalk

I think taking that ota might have made your device incapable of flashing the recovery ur trying.
Sent from my ATRIX HD using Tapatalk

G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24000XCM
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Boot menu selected
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: D42FFD0102000100000000000000
(bootloader) cid: 0x0e
all:
finished. total time: 0.083s

U should be able to flash a recovery since your BL is unlocked. What exploit did u use to unlock it? I know myth tools can help with most Motorola's.
Sent from my ATRIX HD using Tapatalk