Database Info

[Q] how to update rooted Xoom to 3.1 or 3.2

dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..

Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.

is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!

incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.

prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.

i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.

Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,

okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,

prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...

k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.

is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.

thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..

adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...

big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.

big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.

okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.

Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle

[Q] huge boot problem

hello everyone
here's my problem
i've managed to root and install revolution HD rom but i don't know how while trying to instal brobot's metro ui
the tab wont boot and now i can't even manage to access to the boot screen ( the tablet stay at the Eee pad logo + nvidia) and i can't do anything with CWM as it can't read external SD card, no backup (with another rom or the original ics rom) and can't access to the internal storage from my computer
somebody can help me to fix this bloody hell ?

NvFlash for Sbkv1/2
If you have a slider or tf101G You'll have to try to get adb working, try universal naked drivers.
Then you should update your recovery to something that reads ext and int, so this doesn't happen again

ok i'm going to try this solution thanks ^^
will it work under Win 7 x64 ?

What are the first 3 characters of your serial-number?
If they start with B70 (Or a higher number/letter) It's linux only for now (Sbkv2)
If they start with B60 (Or a lower number) It's windows too (Sbkv1)

Thing O Doom said:
What are the first 3 characters of your serial-number?
If they start with B70 (Or a higher number/letter) It's linux only for now (Sbkv2)
If they start with B60 (Or a lower number) It's windows too (Sbkv1)
Click to expand...
Click to collapse
how can i see that when my tab won't boot and i can only access the recovery menu ?

Its on the box you purchased it in or on a clear sticker that runs along the bottom of the back of it.
When did you buy it?

is there any way that i can access the internal storage of my TF101 while it is in CWM ?so i can throw a safe rom in there
with a win7 x64 computer

magingl said:
is there any way that i can access the internal storage of my TF101 while it is in CWM ?so i can throw a safe rom in there
with a win7 x64 computer
Click to expand...
Click to collapse
If your computer recognizes the tablet as ADB in recovery then you can do it that way. What version of ARHD are you using. i can create a proper version for you

mrevankyle said:
If your computer recognizes the tablet as ADB in recovery then you can do it that way. What version of ARHD are you using. i can create a proper version for you
Click to expand...
Click to collapse
the very last one

magingl said:
the very last one
Click to expand...
Click to collapse
OK the metroUI on brobot's site is for ARHD3.2 not ARHD3.4 and thats what caused our problems it will take me a while to download ARHD but once i have it the file should be up pretty quick

mrevankyle said:
OK the metroUI on brobot's site is for ARHD3.2 not ARHD3.4 and thats what caused our problems it will take me a while to download ARHD but once i have it the file should be up pretty quick
Click to expand...
Click to collapse
so with your software i will be able to access to inner storage of the TF101 and put a clean rom inside ?

magingl said:
so with your software i will be able to access to inner storage of the TF101 and put a clean rom inside ?
Click to expand...
Click to collapse
No. You need to install the android SDK. Then plug the device into the computer in recovery. You can try to mount usb there. Or run adb devices in command prompt then push the systemUI and framework-res through there.
this is the format
adb push <local> <remote>
code will be something like this
adb push systemUI.apk /system/app/systemUI.apk
and
adb push framework-res.apk /system/framework/framework-res.apk
all i was doing was fixing metro UI so that you can install it without bricking

mrevankyle said:
No. You need to install the android SDK. Then plug the device into the computer in recovery. You can try to mount usb there. Or run adb devices in command prompt then push the systemUI and framework-res through there.
this is the format
adb push <local> <remote>
code will be something like this
adb push systemUI.apk /system/app/systemUI.apk
and
adb push framework-res.apk /system/framework/framework-res.apk
all i was doing was fixing metro UI so that you can install it without bricking
Click to expand...
Click to collapse
I should use Eclipse then ?

magingl said:
I should use Eclipse then ?
Click to expand...
Click to collapse
um no just ADB you do not need to exit anything java. That code goes into command prompt

Allways worked for me
1) http://forum.xda-developers.com/showthread.php?t=1622628
2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)

Cascabreu said:
1) http://forum.xda-developers.com/showthread.php?t=1622628
2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)
Click to expand...
Click to collapse
The first would delete his data which he does not want and the second is not the cause of the problem
The issue is that by flashing a theme that pushes in an incompatible systemUI and framework-res causes the tablet not to boot. The problem is kind of like putting the wrong engine in a car so that it still looks fine and almost everything is in tact but it will not start

mrevankyle said:
The problem is kind of like putting the wrong engine in a car so that it still looks fine and almost everything is in tact but it will not start
Click to expand...
Click to collapse
LOL I love that Analogy, yeah if it was MetroUI that broke it then flashing right UI files will fix it. Unless he already wiped.

This should fix it.
View attachment 1097888
Thing O Doom does this update script look fine to you a haven't really done many
Code:
mount("ext4", "/dev/block/mmcblk0p1", "/system");
package_extract_dir("system", "/system");
unmount("/system");
and Magingl if you have a microSD try to put that into your computer via an adapter or phone and transfer the clean rom or my file then use that to flash via CWM otherwise push this file with ADB to /sdcard

Yeah that script is good.
run_program("/sbin/busybox", "mount", "/system");
also works. XD Yours is less lazy though.

I'm kinda noobish but i don't know how to access the adb console

Need help - stupid mistake

Well to make it short and simple. I did a factory reset on my tablet and i had seanz rom running. Now all it did was just get stuck at the nexus loading screen. I went into cwm and wiped everything out. So now it gets stuck at the asus boot screen. I don't have a backup in my tablets internal storage. So im trying to use my sd card. But I can't figure out how to get CWM to read my sdcard. Is there anyway i can fix this problem?

1. Wrong forum. This should be in the Q&A section.
2. CWM (and TWRP for that matter) does not support the external SD card. You will have to ADB push the ROM you want to flash to your internal storage. There are lots of threads in the TF300 section about doing so, filled with instructions and troubleshooting tips.

EndlessDissent said:
1. Wrong forum. This should be in the Q&A section.
2. CWM (and TWRP for that matter) does not support the external SD card. You will have to ADB push the ROM you want to flash to your internal storage. There are lots of threads in the TF300 section about doing so, filled with instructions and troubleshooting tips.
Click to expand...
Click to collapse
Sorry about that. I'll go check it out thanks. Feel free to move or delete the thread.

cmw at the moment doesn't support external sdcards. go into recovery and adb push c:\romfolder\rom.zip /sdcard
Sent from my ASUS Transformer Pad TF300T

Hey heres a tutoral I wrote for flashing back to stock or if stuck between roms

currently adb pushing file to sd card. Ill post back with an update
UPDATE: so I did an adb push of the rom file, but when i go to search for the file, CWM tells me: couldn't open directory, no files found

if all fails then try using adb in linux, most likely a ubuntu live cd(which is free).
Sent from my ASUS Transformer Pad TF300T

joshrod921 said:
currently adb pushing file to sd card. Ill post back with an update
UPDATE: so I did an adb push of the rom file, but when i go to search for the file, CWM tells me: couldn't open directory, no files found
Click to expand...
Click to collapse
I know it sounds weird, but at time when i did it id go looking for the file and it was no where to be found but if you push the file twice it will show up in the folder you selected, it had me a bit worried when i was doing it and couldnt find it, but trust me it works

d_crossfader said:
I know it sounds weird, but at time when i did it id go looking for the file and it was no where to be found but if you push the file twice it will show up in the folder you selected, it had me a bit worried when i was doing it and couldnt find it, but trust me it works
Click to expand...
Click to collapse
I'll try that and see if it works. If not im gonna use ubuntu and try it there. This really sucks for me lol.

Got it working woot!!!!!!
I found someones post here: http://forum.xda-developers.com/archive/index.php/t-1601802.html
in a nutshell, i pushed the blob file of the rom, then used this command as told in the instructions: adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4. I rebooted and bam back to stock completely. Now to flash Seanz rom and make a rom folder in my storage. Thanks everyone for your help!

joshrod921 said:
Got it working woot!!!!!!
I found someones post here: http://forum.xda-developers.com/archive/index.php/t-1601802.html
in a nutshell, i pushed the blob file of the rom, then used this command as told in the instructions: adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4. I rebooted and bam back to stock completely. Now to flash Seanz rom and make a rom folder in my storage. Thanks everyone for your help!
Click to expand...
Click to collapse
Congrats I know the relief !

d_crossfader said:
Congrats I know the relief !
Click to expand...
Click to collapse
I'm glad its working now. I'm leaving for a week long trip Sunday, and I was planning on bringing my tablet with me. Learning from my mistake and moving on.

System backup please?!

Hi people. Ive just bricked my Relay by installing Chainfire3D(dont laugh at me I know im stupid)))). So can anyone do a backup the system by Recovery mode and send me to my email [email protected] or attach it here, I will put it in my SD and do a restore from recovery mode(i didnt brick it fully, I guess its called softbrick).
I would really appreciate anybodies help. Please people I really need help...Thanks in advance)))

Just flash a new ROM in recovery, or if you plan to just do a restore of a system partition you would need to give out more information as to flash the correct one as each ROM will have a different system partition

the cavaca
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.

SuddenGun007 said:
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
Click to expand...
Click to collapse
Thanks man, really appreciate your help.

HaykKarapetyan said:
Thanks man, really appreciate your help.
Click to expand...
Click to collapse
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.

SuddenGun007 said:
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
Click to expand...
Click to collapse
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2

HaykKarapetyan said:
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
Click to expand...
Click to collapse
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.

SuddenGun007 said:
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
Click to expand...
Click to collapse
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions

HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
605 MB I should have said......what I meant was that in your first reply you told to install rom and then flash recovery and I dont think all that is done by only these 5 steps

HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK. It really is a 3 step process, but since you soft-bricked your phone you can't simply copy the stock-system.zip to your sdcard and flash that in recovery. You will need adb to communicate with your phone while in recovery.

SuddenGun007 said:
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK.
Click to expand...
Click to collapse
So in 5th step I should locate to that 605mb.zip,without extracting it

stimuli erpio
HaykKarapetyan said:
So in 5th step I should locate to that 605mb.zip,without extracting it
Click to expand...
Click to collapse
Yes that is correct, the recovery when it installs will unpack it for you.

SuddenGun007 said:
Yes that is correct, the recovery when it installs will unpack it for you.
Click to expand...
Click to collapse
Alright man, thanks. Still installing the freaking drivers)))

HaykKarapetyan said:
Alright man, thanks. Still installing the freaking drivers)))
Click to expand...
Click to collapse
I am using Linux, otherwise I would try to send you the drivers.
You might be able to use this http://www.solvusoft.com/en/update/drivers/mobile-phone/samsung/t-mobile/sgh-t699/model-numbers/

SuddenGun007 said:
I am using Linux, otherwise I would try to send you the drivers.
Click to expand...
Click to collapse
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))

HaykKarapetyan said:
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
Click to expand...
Click to collapse
Oh crap I didnt see you had a link there, let me check that one out

This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.

SuddenGun007 said:
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
Click to expand...
Click to collapse
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???

HaykKarapetyan said:
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
Click to expand...
Click to collapse
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo

SuddenGun007 said:
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
Click to expand...
Click to collapse
Ok so if I download this and lets say put this zip in c:\Android what command should I run in cmd???

[Q&A] EasyFlasher - Install CWM/Root/unbrick in one click! [ALL TF101][NVFLASH]

Q&A for EasyFlasher - Install CWM/Root/unbrick in one click! [ALL TF101][NVFLASH]
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:

I though my model was tf101. It was tf201. I brick it! None of the tutorials of this website seems to work. There's a way to unbrik the tf201 bricked with this software?

DavidTG said:
I though my model was tf101. It was tf201. I brick it! None of the tutorials of this website seems to work. There's a way to unbrik the tf201 bricked with this software?
Click to expand...
Click to collapse
http://forum.xda-developers.com/transformer-prime
http://forum.xda-developers.com/showthread.php?t=1514088

*Detection* said:
http://forum.xda-developers.com/transformer-prime
http://forum.xda-developers.com/showthread.php?t=1514088
Click to expand...
Click to collapse
I think my situation is option 2 or 3. There's no guide for that. Also, I can get into recovery mode. If I could do that, I could do option 1!

Where to get TF101 EasyFlasher, or recommended alternative?
Decided to finally root/flash my old TF101. Was following Frederuco's Guide, downloading all the bits and pieces, but the download link in the EasyFlasher thread doesn't work. Search didn't yield anything except posts in that same thread, and none of the most recent posts mention an alternate download location or a new flashing tool to use.
Any help is appreciated.

Help with Easyflasher
I want to flash the Asus stock ROM using Easyflasher.
I downloaded the latest version of Easyflasher on to my Windows 8.1 laptop. I run the app as an Administrator and follow the instructions. Once Easyflasher has completed its operation, I reboot the tablet, but nothing has changed! The tablet is still in the same way. Does anyone have any ideas?

st1974 said:
I want to flash the Asus stock ROM using Easyflasher.
I downloaded the latest version of Easyflasher on to my Windows 8.1 laptop. I run the app as an Administrator and follow the instructions. Once Easyflasher has completed its operation, I reboot the tablet, but nothing has changed! The tablet is still in the same way. Does anyone have any ideas?
Click to expand...
Click to collapse
Did you add the Stock ROM to Easyflasher folder and did you put the TF into APX mode?

*Detection* said:
Did you add the Stock ROM to Easyflasher folder and did you put the TF into APX mode?
Click to expand...
Click to collapse
Yes, run as Administrator, Naked drivers installed, Stock ROM added to the Easyflasher folder and put into APX mode. I have no idea what's going on. Your thoughts?

Which OS are you running? If it's Win 8.x or 64bit, disable driver signing at boot
Did you check you had selected the correct SBK version in Easyflasher?
SBK1 is B6O and previous (Some B7O) serial numbers, anything higher is SBK2

bricked TF101 easy flasher problem
I've done everything in the video on youtube video (youtube . com/watch?v=25i0H43cTqgzz)
but keep getting now where, gets this message every time...any ideas?
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!

upwardseven said:
I've done everything in the video on youtube video (youtube . com/watch?v=25i0H43cTqgzz)
but keep getting now where, gets this message every time...any ideas?
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!
Click to expand...
Click to collapse
The ROM you downloaded from ASUS, the stock one, it comes double zipped, did you extract the first one before putting it into the Easyflasher folder?
I can't remember which way around it's meant to be, but if you didn't extract it first, try extracting it once and putting the extracted zip in the Easyflasher folder
If you did extract it first, try just putting the original direct downloaded zip from ASUS into the folder instead
Been so long since I had stock installed I can't remember, but it looks like that's the problem according to your error messages
Any reason you are returning to the buggy rebooting SOB RR stock ROM when there are 100x more stable custom ROMs like KatKiss 4.4.4 #36 ?

*Detection* said:
The ROM you downloaded from ASUS, the stock one, it comes double zipped, did you extract the first one before putting it into the Easyflasher folder?
I can't remember which way around it's meant to be, but if you didn't extract it first, try extracting it once and putting the extracted zip in the Easyflasher folder
If you did extract it first, try just putting the original direct downloaded zip from ASUS into the folder instead
Been so long since I had stock installed I can't remember, but it looks like that's the problem according to your error messages
Any reason you are returning to the buggy rebooting SOB RR stock ROM when there are 100x more stable custom ROMs like KatKiss 4.4.4 #36 ?
Click to expand...
Click to collapse
Yes I tried both unzipping once and also the direct download also tried the ww tw and us downloads and still nothing. The reason I'm doing this is because somehow during katkiss 4.4.4 I bricked it so I'm at a loss

I'd try an NVFLASH ROM then, that completely deletes and recreates all partitions on the TF, formats everything, and installs a ROM afterwards
Here's the last ICS WW version
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Basically the same routine as Easyflasher, stick the TF into APX mode, make sure the naked drivers are installed and device manager sees the TF when it's in APX mode
Then run download.bat as Admin (Right click > Run as Administrator)
It takes a while to send everything over USB, so be patient
If this doesn't work - there must be another problem somewhere

*Detection* said:
I'd try an NVFLASH ROM then, that completely deletes and recreates all partitions on the TF, formats everything, and installs a ROM afterwards
Here's the last ICS WW version
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Basically the same routine as Easyflasher, stick the TF into APX mode, make sure the naked drivers are installed and device manager sees the TF when it's in APX mode
Then run download.bat as Admin (Right click > Run as Administrator)
It takes a while to send everything over USB, so be patient
If this doesn't work - there must be another problem somewhere
Click to expand...
Click to collapse
ok so I got it back up and running now are there any quick and easy way to root and intsall katkiss 4.4.4 ?

upwardseven said:
ok so I got it back up and running now are there any quick and easy way to root and intsall katkiss 4.4.4 ?
Click to expand...
Click to collapse
Theres a few apps that can root, but you're gonna need TWRP installed again too before flashing KK 4.4.4
Personally I'd try Easyflasher again now you have the TF up and running, if that still fails, try the following:
Try one of these to root
http://forum.xda-developers.com/showthread.php?t=2658335
https://towelroot.com/
AVs might detect this as malware, it's not
http://www.kingoapp.com/android-root.htm
Then download TWRP blob 2.3.2.3
http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Stick it on /sdcard and rename to twrp.blob
Install and Open 'Terminal' on the TF, and type these commands, reboot fully after to complete the install before entering recovery
https://play.google.com/store/apps/details?id=jackpal.androidterm
Code:
# su
<Grant SuperUser permission if it pops up>
# dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
# reboot
All being well you should now be able to enter TWRP and flash KK 4.4.4
Probably a good idea to make a full Nandroid backup in TWRP of this stock ROM before flashing anything else, so if it all goes t1ts up again, you can just restore

*Detection* said:
Theres a few apps that can root, but you're gonna need TWRP installed again too before flashing KK 4.4.4
Personally I'd try Easyflasher again now you have the TF up and running, if that still fails, try the following:
Try one of these to root
http://forum.xda-developers.com/showthread.php?t=2658335
https://towelroot.com/
AVs might detect this as malware, it's not
http://www.kingoapp.com/android-root.htm
Then download TWRP blob 2.3.2.3
http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Stick it on /sdcard and rename to twrp.blob
Install and Open 'Terminal' on the TF, and type these commands, reboot fully after to complete the install before entering recovery
https://play.google.com/store/apps/details?id=jackpal.androidterm
Code:
# su
<Grant SuperUser permission if it pops up>
# dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
# reboot
All being well you should now be able to enter TWRP and flash KK 4.4.4
Probably a good idea to make a full Nandroid backup in TWRP of this stock ROM before flashing anything else, so if it all goes t1ts up again, you can just restore
Click to expand...
Click to collapse
alright I don't know what I'm doing wrong but none of those work. Easyflasher is not doing a thing, towelroot force closes, baidu root the download for en 2.3.7 isn't working and 2.3.6 is in chinese, I followed his direction and got a check once it was done but root checker showed no root. Kingo root fails each time I try

upwardseven said:
alright I don't know what I'm doing wrong but none of those work. Easyflasher is not doing a thing, towelroot force closes, baidu root the download for en 2.3.7 isn't working and 2.3.6 is in chinese, I followed his direction and got a check once it was done but root checker showed no root. Kingo root fails each time I try
Click to expand...
Click to collapse
Give Peri a try
http://forum.xda-developers.com/showthread.php?t=1681155

*Detection* said:
Give Peri a try
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
gave that one a try and got to flashing and it says /dev/block/mmcblk0p4: cannot open for write: Permission denied so when i continue and it tries to go into recovery I get the android with the caution sign in him.

Are people still supporting this?
Please disregard! don't know how to delete this!

Forgot attachments!
Sorry i forgot the attachments in the previous post, and i cant figure out how to add them there, or delete the post, so i just replied and had everything added here.
AGoonyGooGoo said:
Hello,
I have a received a bricked Transformer Tf101 that is sk1 with model number b40.
I'm trying to use easyflasher 0.8.3.b-STABLE,
I have placed this firmware in the asusupdate folder of easyflasher: WW_epad-user-9.2.1.27 (i did not unzip it)
The naked drives are installed correctly and its in APX mode (See attachment 1)
I then select SBK1 because my S/N begins with b40.
I then click "Flash Asus Stock/Unzip."
Then the prompt comes up and i tried both options "a" or "u" with the same result (see attachment 3)
Then it crashes (see attachment 4)
After selecting close program, it gets to this point and freezes (see attachment 2)
And my asus also freezes (See attachment 5)
From here I have no option but to shut everything down.
I have been working on this for a week now. Can anyone please, PLEASE help me? This will save me a lot of trouble with school by being a vessel for my ebooks so I dont have to spend 500 a quarter on new books. All help is a deeply appreciated.
Click to expand...
Click to collapse