This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
Related
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
flameinthefire said:
after unlocking thru the ez tool installed twr recovery and installed the synergy rom and its just stuck on samsung galaxy s logo please help what do i do?
Click to expand...
Click to collapse
Sounds like an bootloop, just odin back to stock and try again.
If you remove the battery and turn it back on, will it boot into recovery?
power+vol up+home button
Karl said:
power+vol up+home button
Click to expand...
Click to collapse
yes it turns back on but i have unlocked it and its on twp recovery which rom would work with it?
i tried flashing mr beans rom that didnt work beacuse i am on twp recovery and i tried flashing synergy rom that didnt work either so wat should i do. since i unlocked the phone can i still do odin? or will that brick my phone
guys please help!
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
is there any rom that i can use for my unlocked s3
flameinthefire said:
guys please help!
Click to expand...
Click to collapse
Someone already told you what to do. Find a stock ROM, boot up Odin and flash.
the roms you tried work with TWRP... ive used TWRP since release
Karl said:
the roms you tried work with TWRP... ive used TWRP since release
Click to expand...
Click to collapse
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Locked or unlocked phone shouldn't matter as far as the Rom is concerned, it's been stated many times that the kexec kernels will boot fine on an unlocked phone. I would suggest starting fresh, stock ODIN, root, unlock, then flash CWM 6.0.1.0 with ez recovery and go from there.
Some people are not having any issues with the touch recoveries and others are, in my experience the CWM recovery has been the most stable and I could really care less about "touching" my recovery, buttons do the same thing. Just my 0.02
Sent from my Galaxy S III using Xda Premium
feel like an old man hearing these stories......we all know them...when we first started out flashing and **** went wrong....freak outs..panics....sweating..pacing..anger....regret.........BUT then you work through them and look back and say "**** that was easier than I thought"....and we come across them again without panic or hesitation........................dude relax........
1-grab a stock image...chose anyone you want in these forums..some are even prerooted.....i personally got competely back to stock
2-i use the one click root method..so root
3-flash cmw...any version you want as long as it is made for your model phone.....you can use e-z recovery app from market
4-MAKE A ****ING BACKUP!!! very important...
5-download e-z unlock from the play market..use...and done..now you are stock, rooted, unlock bootloader......if you plan on flashing cm10 or aokp or aosp....please make sure to read the thread "how to backup your imei" before flashing any of those roms.............boom goes the dynamite:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh:.............................
King_tee said:
I don't think they work with TWRP. They will flash fine but they wont boot. I had the same problem as the OP when i flashed them. I guessing its because they aren't setup for unlocked phones yet. OP all you need to do is wipe using TWRP then flash the cyanogen mod 10 leak posted by CVPS. Make sure you flash gapps and you will be good to go.
Click to expand...
Click to collapse
Kexec roms don't but synergy should have. I use twrp and Synergy no problem. There isn't anything special that has to be setup for an unlocked bootloader.
Op you should be able to flash any non kexec rom. Did you do a wipe factory reset? If not you may want to give that a try
Sorry for my english...
Today i unlock the tf300t bootloader and i root it... I flash the Custom Rom JB Hydro 4.1 (i did the ota jb) ... After i want try the cm10... i flash it but it doesn't work... The tab don't work.. i see the bootlogo ... The cmw work, so i tried to restore to jb hydro... but it doesn't work... Now how can i resolve?
hi !
In the recovery mod, try to wipe dalvik, cache and data after that flash your rom again...
if you can try CWM or TWRP recovery ...
I'm having the same Problem
Today i went to CyanogenMOD site and downloaded the most resent Nightly build of Cm10, flashed it into my TF300T and now im stuck in Boot Loop. I used CWM to make a full rom backup before than, but when i do restore from backup everythign goes well, until i reboot it, then it hangs in boot loop again. What can i do? (I followed more than 3 tutorials step by step so i dont know what went wrong. It was OTA JB 4.1.1 , then i unlocked bootloader and rooted, then i did stock rom backup with cwm and then i flashed cm10 nightly and issues started. =(
ozkrtech said:
Today i went to CyanogenMOD site and downloaded the most resent Nightly build of Cm10, flashed it into my TF300T and now im stuck in Boot Loop. I used CWM to make a full rom backup before than, but when i do restore from backup everythign goes well, until i reboot it, then it hangs in boot loop again. What can i do? (I followed more than 3 tutorials step by step so i dont know what went wrong. It was OTA JB 4.1.1 , then i unlocked bootloader and rooted, then i did stock rom backup with cwm and then i flashed cm10 nightly and issues started. =(
Click to expand...
Click to collapse
There is no way of flashing Cyanogen JBs if you are on stock JB. Only Rom available for you is Hydro JB. All otheres are not flashable until the Cyanao Crew get the new Kernel and bootloader to run.
Did you do a full-wipe (wipe data, cache, dalvik-cache, and system) if you did, try TWRP recovery 2.2.2.0 it might say it wiped, but it might be leaving some data behind or you can try a double wipe. I usually wipe front to back, but some people wipe back to front.
Sent from my Nexus 7 using XDA Premium HD app
What can i do?
sammael1069 said:
Did you do a full-wipe (wipe data, cache, dalvik-cache, and system) if you did, try TWRP recovery 2.2.2.0 it might say it wiped, but it might be leaving some data behind or you can try a double wipe. I usually wipe front to back, but some people wipe back to front.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
.
ozkrtech said:
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
Click to expand...
Click to collapse
Ok.. I solved it... I downloaded the fw from asus site... And i flashed blob file with fastboot.. Now my pad works
ozkrtech said:
The only reason i tried CM10 was to overclock using ezoverclock (if thats possible) because it failed to OC on Stock JB due kernel changes.
Can I overclock using ezoverclock on Hydro JB?
Why didn't my Stock rom backup work either?
Click to expand...
Click to collapse
EZ is not working on Hydro. No OC possible till now.
Im going back to stock then.
mikaole said:
EZ is not working on Hydro. No OC possible till now.
Click to expand...
Click to collapse
Ok then, im going to download stock JB from Asus site , and after it boot ur and start running smooth im goign to restore backup, and hope it all return normal, thanks for the help, i let ya'all know if it worked.
Edit: I downloaded stock firmware from Asus site and extracted the blob file, moved blob file to c:\Fastboot, then put tablet in fastboot mode via recovery, and flashed blob following this instructions to make it work again.
"U could reflash your unit with stock ROM using fastboot. I just unbricked my unit doing that after 5 days of fighting.
This is what I did, I downloaded job update from Asus then moved the blob to c/fast boot, loaded unit to fast boot then typed
fastboot -i 0x0B05 flash system blob
But make sure our boot loader is 10.4 or it will signature mismatch, so down load the appropriate boot loader .
That's what I did at least and my unit is working again. "
So i'm happy again, thanks for support xda-developers !!! (the instructions in the quote are also from xda-developers)
I was on locked on stock OTA JB.
I unlocked a few days ago, then last night flashed TWRP. Created a nandroid, then rooted.
Today I've spent several hours downloading ROMs, doing Titanium backups, surfing forums, backing up my personal files etc. i.e. using my tablet normally without problems.
I decided it was time to flash a ROM so booted in TWRP to create a fresh nandroid. Then when it finished I rebooted the system with the plan to copy the nandroid to my pc.
The tablet booted, but then after 30s or so rebooted. It's now stuck in this boot loop. So I tried a cold boot, and then restoring the latest nandroid and the problem persists. I'm currently trying to restore the pre root nandroid I made.
To recap - I am on stock OTA JB, with TWRP v2.3.1.0 recovery. Any thoughts?
Ok just to update - the pre root nandroid seems to be stable at the moment. So... What to do?
Should I reflash the recovery? Try a different recovery?
Any ideas why the nandroid would be borked when the system seemed stable when I created it?
Sent from my Galaxy Nexus using Tapatalk 2
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
No it doesn't, it just replaces stock recovery and allows you to gain root.
You could start your own thread. Or, you could read the thread in Android Development that gives clear instructions for noobs to gain root and install TWRP or CWM.
Sent from my Galaxy Nexus using Tapatalk 2
which ROM were you trying to flash? was it a JB rom?
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
After you install TWRP, you just need to flash a root zip file with TWRP to gain root..
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
Flash a rooted custom rom. ull gain root + rom easily
mike-y said:
which ROM were you trying to flash? was it a JB rom?
Click to expand...
Click to collapse
Since this thread got immediately hijacked i'm not sure but I'm going to assume this part of your post was aimed at me...
I wasn't trying to flash a ROM at all. I hadn't even got that far. All I'd done was flash the recovery, root it and then create a nandroid. It was creating the nandroid that seemed to trigger the boot loop, even though that makes zero sense.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
can you get back into fastboot connected to your PC?
I'd try to re-flash TWRP. Also make sure you are using the JB version, not the ICS version.
http://teamw.in/project/twrp2/97
I just unlocked and flashed TWRP on my tf300 (with the OTA JB update) this morning, and everything is working fine. I also flashed a root file without any issue.
I reflashed TWRP and re-rooted it seems to be OK.
Then I found I couldn't get any ROMs to work - they all froze at the boot screen. The solution to that problem lies in flashing the US update of JB rather that the WW. Now I'm running Hydro with Untermensch's kernel.
One thing I did notice with TWRP 2.3 is I get the error "can't mount /storage" in the log whenever I do anything. A bit of research suggests this might be an issue with TWRP 2.3, not present in 2.2. I wonder if that is what was causing the boot loop issue I had previously.
I can't seem to find a blob of 2.2 to downgrade to so I'm living with it for now and hope it's not going to cause problems down the line.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Good that TWRP always using the same names for a DL Link. So here is the 2.2 for JB Bootloader
If you are looking for ICS just edit the dl link .
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300tg-JB.blob
Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob