Database Info

Neither Win7 nor Mint recognise TF101 by USB since updating to ICS

I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?

+1
But since i transfer my data via Dock/USB it's not a big issue atm.

jordivf said:
I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?
Click to expand...
Click to collapse
My B50 was recognized by Win7 after successfully installing the device driver. A TF101 Drive was created with SD and External Storage available. I have a stock ICS, no root and no custom roms.

Mine did to. Although I had to go into device manager and uninstall the replug mine in and they reinstalled themselves. All but one that I can remember off hand but I just double-clicked it and it installed the 2nd time.

I had same issue... if you used CWM flashable package, you need to reflash bootloader. I've found link in dev section. From then everything is just fine.
Sent from my ICS TF101 by XDA HD app

You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
reupload: http://www.mediafire.com/?h4pgduf8zsgmh96
E: gnufabio (Revolver ROM) use this boot image in his ROM, I think you can use this package for your US version TF

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.

josteink said:
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.
Click to expand...
Click to collapse
It was the WW version I tried but still no joy.

michael_duvalle said:
It was the WW version I tried but still no joy.
Click to expand...
Click to collapse
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)

josteink said:
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)
Click to expand...
Click to collapse
Yes. I was originally on Prime 2.1.0, flashed ww-9.2.1.11-CWM-full-rooted.zip, then flashed ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip on top. No wipes were performed and everything else except the battery usage is working properly.

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
You, Sir, are a genius.
Yup! That sorted the issue.

michael_duvalle said:
Yes. I was originally on Prime 2.1.0,
Click to expand...
Click to collapse
No wipes were performed
Click to expand...
Click to collapse
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.

schauol1 said:
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.
Click to expand...
Click to collapse
What would be the best way to fix this then. Should I revert to Honeycomb stock and update the official way or shall I just wipe and reflash ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip. Also, If I did the second method, what exactly should I wipe?
Cheers

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.

jozka.1 said:
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.
Click to expand...
Click to collapse
When you mean extract blob from the zip and place to the root of SD, do you mean the internal SD or the Removable SD?

It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)

jozka.1 said:
It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)
Click to expand...
Click to collapse
I tried it in terminal and it said that the file was written in several seconds. Several minutes later I went back to it, rebooted and still no joy.

And before boot system did you saw flash new blob file?

jozka.1 said:
And before boot system did you saw flash new blob file?
Click to expand...
Click to collapse
Yes. I left terminal open for about 10 minutes, then rebooted.

[Q] Recovery

Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?

thinkhope said:
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
Click to expand...
Click to collapse
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.

absolutelygrim said:
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
Click to expand...
Click to collapse
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.

thinkhope said:
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
Click to expand...
Click to collapse
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know

absolutelygrim said:
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
Click to expand...
Click to collapse
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.

thinkhope said:
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
Click to expand...
Click to collapse
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot

absolutelygrim said:
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
Click to expand...
Click to collapse
Thank you very much!!
Sent from my One X using xda app-developers app

Trying to update to 4.4.2 via TWRP Flash getting error

I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?

On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful

tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.

matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update

jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.

matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format

jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.

matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything

http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk

Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.

jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?

matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it

jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks

TWRP 2.6.3.0 not mounting anything...

So in my attemts to in stall CM 11 (http://forum.xda-developers.com/showthread.php?t=2570965) I have ruined mt tablet.
This is what I did.
1.Flashed TWRP 2.6.3.0 via (http://teamw.in/project/twrp2/97) I down loaded that latest .blob file and flashed with fastboot.
2. booted into TWRP
3. nothing would mount.... shutdown.
4. booted into my curent PAC Rom 4.3
5. Rebooted straight into recovery from the rom (I thing this is what screwed the pooch)
6. Boots into TWRP and only into TWRP but nothing is mounted. I cant get into fastboot to install the old recovery and 2.6 doesnt see any drives.
Any help would be great!

bucket81 said:
So in my attemts to in stall CM 11 (http://forum.xda-developers.com/showthread.php?t=2570965) I have ruined mt tablet.
This is what I did.
1.Flashed TWRP 2.6.3.0 via (http://teamw.in/project/twrp2/97) I down loaded that latest .blob file and flashed with fastboot.
2. booted into TWRP
3. nothing would mount.... shutdown.
4. booted into my curent PAC Rom 4.3
5. Rebooted straight into recovery from the rom (I thing this is what screwed the pooch)
6. Boots into TWRP and only into TWRP but nothing is mounted. I cant get into fastboot to install the old recovery and 2.6 doesnt see any drives.
Any help would be great!
Click to expand...
Click to collapse
To install CM11, you need the TWRP posted in the guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7

cmendonc2 said:
To install CM11, you need the TWRP posted in the guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
Thanks but I cant get into Fastboot to flash that version. Is there a way I can use the flashable zip? I cant mount anything in my curent version of TWRP.

bucket81 said:
Thanks but I cant get into Fastboot to flash that version. Is there a way I can use the flashable zip? I cant mount anything in my curent version of TWRP.
Click to expand...
Click to collapse
You can try. You must be on 10.6.1.15 or above to flash the kitkat zip though.

cmendonc2 said:
You can try. You must be on 10.6.1.15 or above to flash the kitkat zip though.
Click to expand...
Click to collapse
Is there a TF300T NVflash recovery tutorial? Like what commands I need and files. I was looking at this (http://forum.xda-developers.com/showthread.php?t=1927818) it doesn't have the right files I don't think.
I have this (https://drive.google.com/#folders/0B2Gy5tiu1Omoa2FjQzBzWWhpWjg)
but no idea how to use it..... and its been a while so I don't really remember NVFlash.

bucket81 said:
Is there a TF300T NVflash recovery tutorial? Like what commands I need and files. I was looking at this (http://forum.xda-developers.com/showthread.php?t=1927818) it doesn't have the right files I don't think.
I have this (https://drive.google.com/#folders/0B2Gy5tiu1Omoa2FjQzBzWWhpWjg)
but no idea how to use it..... and its been a while so I don't really remember NVFlash.
Click to expand...
Click to collapse
Try:
Code:
nvflash --create
This will repartition and format everything back to stock. I think you will have to flash the stock ROM after that but I'm not sure how?

[Q] Signature verification failed OTA Lollipop

I just got the OTA Update to Lollipop
and after i download the files, i press the install and reboot,then my nexus goes to recovery mode (CWM 6)
and then there appears :
. . . (theres still some description)
E:signature verification failed
then i just reboot and get my nexus still on 4.4
im actually forget which ROM im using right now
but in settings , it is KTU84P
FYI : I just unrooted this devices and this happened too when i was trying to upgrade with Nexus Update Checker.
Please help me guys

you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.

jasonftfw said:
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
Click to expand...
Click to collapse
how to make it sure/check it , that im using stock ROM or not
and how to uninstall CWM ?

Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.

jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?

DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.

jasonftfw said:
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
Click to expand...
Click to collapse
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
---------- Post added at 03:01 AM ---------- Previous post was at 02:56 AM ----------
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
just got the OTA notification again, so I'll give it another shot (yeah, i just quoted myself)

DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip

jasonftfw said:
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
Click to expand...
Click to collapse
thanks but I got the OTA notification again and is now installing without problems

DarknessWarrior said:
thanks but I got the OTA notification again and is now installing without problems
Click to expand...
Click to collapse
Never hurts to know how to sideload for future.

jasonftfw said:
Never hurts to know how to sideload for future.
Click to expand...
Click to collapse
agreed.

I just installed Android Sdk and downloaded the ota from google and im having problems it doesnt side load

jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw

Falconite said:
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Click to expand...
Click to collapse
check out the toolkit from wugfresh, that might be the easiest way for you if you don't know what you're doing... maybe take some notes so that you do remember what you're doing for future.