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] Bricked Device? Please Help me!!!!!!!!! im LOST

hi, iam new user of TF300t, i installed the Energy.TF201.or.TF300..JB.03.18.2013.( i dont remebmer is the STOCKED or THEMED) ! after that i wanted to install BAKED_TF300T_BB-8, but the device stay on the boot menu! so what i did , installed the 6.0.2.3 CWM ( [CWM][6.0.2.3 / 5.5.0.4] Official CWM Recovery for JB/ICS + ROOT) ! after that i rebooted the device. Stock in the Asus LOGO! After i rebboted by holding the power menu and volume down, i choosed the wipe option ( i dont know why) and from tht time, it rebbots only in the 6.0.2.3 CWM what ever i do!
For 5 days, i have tried to flash via fastboot twrp.blob, i have pushed the firmware from asus to /sdcard and flashed via fastboot always, i have tried and read similaire problems! didt succed! i have always the message tht Can not mount sdcard! cant mound E/data! cant mount anythingg!! What ever i do, always reboot to this CWM !!!!!
please any one help me!!!!!!! thanks a lot!!!

You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.

sbdags said:
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
Click to expand...
Click to collapse
but i can use adb commands, and fastboot commande ( except tht i have waiting for device each time) so its bricked for EVER?!

You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........

sbdags said:
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
Click to expand...
Click to collapse
yes, it accept nothing! even if i downgrade to ics to apply the nvflash its worse! so should i say bye forever to my tf300t?!! if yes, which tablets tht cn be less bricked than others? thks a lottt! wht would u do if u were at my place? thksssssssssss

buy a new mainboard (motherboard)
Sent from my TF300T using xda app-developers app

How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?

Ti2 said:
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Click to expand...
Click to collapse
thanks for yr reply ill try even im bricked! ill by another tabelt but not asus, maybe samsung, i have a GS2 , i install every thing without problem, i think there tables dont brick easly! true?

You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.

Ti2 said:
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Click to expand...
Click to collapse
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
Wrong? No.
Harsh? Yes.
Read read read. Learn learn learn. Then read some more. When unsure, ask questions. Don't just try, then read the manual tot learn how you screwed up...
I am unsure tot flash 4.1 bootloader based roms through the 4.2 patched TWRP. I am NOT just going to try, I am awaiting an answer for 3 days now.
Is a Tab(2) as easily to brick as a Transformer? Yes it is.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
true wht u said !

Not trying to be harsh but that's why they call it "bleeding edge". You take the risks if you cannot be patient.
Sent from my SCH-I510 using xda app-developers app

hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck

lk2l said:
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
Click to expand...
Click to collapse
no succes to flash anything! always back to cwm 6.0.2.3...

when you type fastboot devices or adb devices can you see the device?

lk2l said:
when you type fastboot devices or adb devices can you see the device?
Click to expand...
Click to collapse
i can see this 0123456789ABCDEF, thts not the device name sure! isn't ? i can flash via fastboot ( sending ok, flashing ok) i flashed the blob file tht comes with the Asus frimwork 10.6.1.8 but nothing, always i go back to the 6.0.2.3 CWM! i flashed the twrp.blob file! same thing! im turning in an empty circle! good for trash??

depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how

lk2l said:
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
Click to expand...
Click to collapse
hope so! thkssssssssssssssssssssss

can you tell me which procedure you do to flash the recovery?
here you can found all I have used to flash my tf300t with the bootloader 4.2.1
fastboot+twrp recovery 2.4.4.0-4.2
is possible your fastboot dosen't work correctly?

Can't mount any partition

Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03

matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD

i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)

matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD

Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change

matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD

i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows

Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.

EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?

http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you

sorry guys today i was very busy, i'll try to solve it tomorrow

matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3

CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem

I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.

pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news

matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD

i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me

matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD

i'll definitely try that method! i'll let you know, thanks guys

matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....

Upgrading from 4.1 to 4.2

I have looked everywhere for help on this subject.
I have rooted my tf300t with unlocked boot loader 4.1, but what are the steps to upgrade to 4.2? I want the latest roms but im stuck with the old 4.1
Do I need to update my TWRP first? I have an old version
If there is a link to show me how please post if not let me know please...im desperate and im going away to Dubai for the xmas period

Found the solution. Please close this thread

olster said:
Found the solution. Please close this thread
Click to expand...
Click to collapse
Could you provide solution please?

Tunameltsalad said:
Could you provide solution please?
Click to expand...
Click to collapse
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.

cmendonc2 said:
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.
Click to expand...
Click to collapse
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.

majorpay said:
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.
Click to expand...
Click to collapse
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/

cmendonc2 said:
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/
Click to expand...
Click to collapse
OK, so with this 4.1 modded tablet, if I take the latest version of 4.2, grab the blob, and do the following:
Code:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Is that going to work, or am I going to end up with a brick?
I know that there has been some warnings on upgrading to 4.1 with 4.2 files, so I want to double check before I make a bookend out of this thing.
EDIT: Pulled the trigger - worked out fine. Now I will install a recovery and we'll be good to go!

Update from 4.1 to 5.0

Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.

jaydotelloh said:
Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.
Click to expand...
Click to collapse
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh

lj50036 said:
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh
Click to expand...
Click to collapse
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!

jaydotelloh said:
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!
Click to expand...
Click to collapse
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh

lj50036 said:
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh
Click to expand...
Click to collapse
Thanks Josh, I think I know what to do now:
Step 1: Set up NVFLASH and get my backup files.
Step 2: Flash the 27.5 Bootloader using fastboot.
Step 3: Flash TWRP openrecovery-twrp-2.8.1.0-tf300t.blob
Step 4: Wipe system/cache, etc
Step 5: Flash Katkiss 5.0
Is this correct? Am i missing any steps in there?
Looks like you're not on hangouts right now, shoot me a message if we can chat. [email protected]

So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?

jaydotelloh said:
So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?
Click to expand...
Click to collapse
If you go to edit your first post and then go to adv edit, there you can add 'SOLVED'
Thx Josh