Database Info

[REQ] Need MZ601 Euro 3G users. READ NOW!

Ok, so after the announcement of the 3.1 update at IO yesterday, were all eagle awaiting the 3.1 update.
For those of us in europe, with 3G xooms we need a different update so don't try flash anything that is currently available.
Second and most important. There are NO Stock boot images for 3G europe, we need someone who has stock recovery to dump it and get in touch with me. WE CANNOT UPDATE IF WE INSTALLED CLOCKWORK MOD.
Once we have a stock recovery image I can post all the stock images for us to flash back to stock for the update.
Use these commands to dump the recovery image (you need to be rooted and/or have a custom kernel like Tiamat (or the one in my thread) installed so you can remount, you may also need to install busybox (use Busybo installer by Stericson from the Android Market, don't forget to open and run it after you install it):
Code:
adb remount
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
adb pull /sdcard/recovery.img
That's it, the image will be on your sdcard and copied to your computer, please upload or PM me a link.
Thanks
Macbots drool as I XOOM through the Galaxy to my hearts Desire.

I had to add "platform" to the path:
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
Click to expand...
Click to collapse
Hope I did it all right after rooting the device (by your manual - thanks in advance for this!).

Riffer said:
I had to add "platform" to the path:
Click to expand...
Click to collapse
You're right, sorry I typed it from memory, will update it now!

That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
(The recovery ramdisk ro.build.version.release says 3.0.1, maybe the boot image is from 3.0? Has the MZ601 got 3.0.1 yet?)

ydaraishy said:
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
Click to expand...
Click to collapse
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
It's also possible that the recovery might be the same as the US one, and the US one runs a differnet kernel to the euro one, so it's not necessarily a problem that it's different.
Oh, and any chance of a link to the recovery image you've dumped? Please.

alias_neo said:
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
No, they should have the same kernel. It's designed that way. (Remember, when you get an OTA, you get a recovery-from-boot.p patch that runs on startup to repatch your recovery image back to stock -- it's deliberately based on the boot image, so the patch is as small as possible)
I didn't dump the recovery image -- look a few posts up (I _still_ don't have a device yet )
ed. And I don't think a US MZ601 is out yet...The above dump looks like it's from a German Xoom, based on ro.product.locale.region.

ydaraishy said:
Has the MZ601 got 3.0.1 yet?)
Click to expand...
Click to collapse
Yes. Mine does have it. Got it without any branding from www.sparhandy.de yesterday.
Should I mention I am german?
alias_neo said:
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
Mine is attached above? Or do you say that to ydaraishy?

Riffer said:
Mine is attached above? Or do you say that to ydaraishy?
Click to expand...
Click to collapse
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?

alias_neo said:
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
Click to expand...
Click to collapse
No, they'll binary patch it like usual.
I split the kernel and ramdisk of the recovery image, then the boot image that you had posted a while back for root, then md5'd both kernel images.

Got my T-Mobile Xoom 3G (3.0.1; MZ601; H.6.1-38-5) today and dumped the recovery.img just after flashing rooted boot.img.
Hope this helps.

Thanks guys, hopefully i can use these to sort something out for us when we get 3.1 update finally.

I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.

MediumO said:
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
Click to expand...
Click to collapse
Your zip you PMd me says boot, recovery and system, surely all 3 can't be stock if you installed clockwork mod to dump it, so which two are stock?

Ok, this one is exactly identical to mine - says Winmerge.

Riffer said:
Ok, this one is exactly identical to mine - says Winmerge.
Click to expand...
Click to collapse
Which one?

I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.

MediumO said:
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
Click to expand...
Click to collapse
That's great. Now we just gotta wait for 3.1 in Europe!

I have been fallowing this forum for a long time and also I got my Xoom from CPW couple of weeks ago and I have to say that I'm really waiting for this update so bad, just because many people has been reviewing it and they say is really a change in performance, sometimes I find that my Xoom is quite heavy, more when I'm trying to surf the web, and sometimes when I come to the forum from it, and I will like to be an active member of this forum as well, I will try to help with anything I can and I just rooted my Xoom with neo guide.
sorry if my english is not so good.
I'm in London at the moment
and Galaxy SII owner as well

Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)

MediumO said:
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
Click to expand...
Click to collapse
There will be non of that frankenfrak here sonny. We get our own 3.1 or we all go down swinging. :-D
Macbots drool as I XOOM through the Galaxy to my hearts Desire.

[GUIDE] Official [unroot] guide here

I have seen a lot of unfinished info on UNROOTING so rather than see a bunch of people stuck like I was last night I thought I would toss a little guide together for everyone.
I take no credit for any guides I post just pitching in, if I help you CLICK me a THANKS!
download the asus firmware from here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
extract the blob from the zip file and put it in your adb folder located at something like:
AndroidSDK/platform-tools/
as you did to root the device.
open cmd promt window type the following and return after each.
\cd
\cd AndroidSDK\platform-tools\
adb devices
*adb your device make sure it is hooked up and id'ing your transformer.*
adb push blob /data/local
adb shell
*at the # type the following*
dd if=/data/local/blob of=/dev/block/mmcblk0p4
*wait a few mins to be safe*
now reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob” file. this will remove the clockwork recovery and put your tablet into BOOTLOOP this is ok.
----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Now that your tablet is stuck in a boot loop, put on the root of the micro sd card on your computer-> the update normally found in the asus/update/ folder from the firmware zip you download from asus. I used the .9 US update and it worked fine, you must then rename it to EP101_SDUPDATE.zip make sure you leave it a zip dont change the extension AND->make sure it is on the root of the card.
Now put your card in your transformer, hold the down volume and power till it prompts you in the upper left about wiping or booting to recovery**> let go and push up on the volume, which will load the factory recovery android with a box and a loading bar *** IF IT IS STILL CLOCKWORK RECOVERY THEN YOU MISSED SOMETHING START OVER DO NOT CONTINUE***> it will begin to flash the update do not bother it turn it off or anything else will take up to 10 mins to complete. it will restart and you will see the bar load again on boot up then it will boot to the asus logo and then to the homescreen and your good.
-Ian

Faved for later use when INeed to RMA
Sent from my Transformer TF101

I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.

Thanks for this. I have been holding off trying to root my Tablet until I had some clear indication that there would be a "way back".
I will PM you a link to V8.2.3.9 US Firmware as soon as it's done uploading to MegaUpload (Aborted as someone beat me to it)

I haven't found a need to root my TF yet as all I need for it is running pretty smoothly.
My phone on the other hand gets flashed with a new ROM every few days.
Great to know that I can go back if I do root one day. Thx

I get to this point...
ianandamy said:
...let go and push up on the volume, which will load the factory recovery android with a box and a loading bar...
Click to expand...
Click to collapse
See the box with a loading bar for about three seconds then the screen switches to the image of the android robot logo and an exclamation point within a triangle. I think its because I accidentally wiped my data last night when I was trying to fix the boot loop issue. I'm about to give up on this one...
Edit: Hey it works great, just make sure you don't add a .zip extension to the E101_SDUPDATE rename.

Big Thanks to ianandamy this works great! Got it up and running. The only problem is that I am being prompted to enter a password in order to get it to the homescreen...The second problem is that I never had a security password in order to access the tablet. I have a feeling this has to do with it being rooted by the previous owner before I purchased the tablet. Would the settings return to how he customized it pre-root? If so the password the tablet is asking for would be the one he set before I ever owned the tablet. How do I get around this?!

worked great, and like the profile pic

Added to ultimate thread. Nice job.

isdnmatt said:
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Click to expand...
Click to collapse
Can someone host it and pm me a link to post

It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip

isdnmatt said:
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
Click to expand...
Click to collapse
GREAT!
I've extrapolated the WW version with that http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip

This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
I'd do it, but I'm lame and don't have a linux box or VM setup .. that and I sold my eeePad to pay for vet bills... something about 'daddy save the puppy' is haunting me now.
P.S. Thanks for the info, just trying to save time if this is possible

sirmx said:
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
Click to expand...
Click to collapse
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.

Segnaro said:
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Click to expand...
Click to collapse
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!

StirCwazy said:
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
Click to expand...
Click to collapse
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.

Segnaro said:
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Click to expand...
Click to collapse
Sorry to be a bit pesky here, but just want to be real sure: Based on ROM work I've done on my Android phone, unrooting is not the same as going back to a stock ROM. Actually the reverse is true: you can apply a stock ROM< and it will effectively unroot the phone.
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?

ewingr said:
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
Click to expand...
Click to collapse
Yes, and after a factory reset it would be like when you just took it out of the box.

Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147

b1ackplague said:
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
Click to expand...
Click to collapse
Yes, I went from 3.1 direct to .9 without any issue.

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

[ROOT] How To Root Rogers HTC One X Qualcomm S4 (for Windows, Mac and Linux)

AS MY EVITA IS CURRENTLY BOOTLOADER LOCKED, THIS SUPERBOOT IS FOR TEST PURPOSES ONLY. USE AT YOUR OWN RISK!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r2 - DOWNLOAD - MD5: 39a02275706d4b034c3c185b5b9b1a82
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
Ensure your bootloader is unlocked using the htcdev unlock process
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
WINDOWS - double click 'install-superboot-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
P
PS Details on how to donate should you wish to do so are in the download topic at MoDaCo.

have a mirror? ...file not found.

JSLEnterprises said:
have a mirror? ...file not found.
Click to expand...
Click to collapse
i just tried it. works for me
edit: nope, didn't work upon actually trying to grab the file
edit: thanks Paul!

Small typo, fixed now.
P

Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.

Superboot should automatically install the Superuser APK in /system/app?
P

JSLEnterprises said:
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Click to expand...
Click to collapse
The folder disappears on the next reboot.
P

paulobrien said:
Superboot should automatically install the Superuser APK in /system/app?
P
Click to expand...
Click to collapse
It did, but didnt show up on first boot. wasnt in the appdrawer, but was in the directory.
either a manual reinstall, or a hot restart fixes it. (Dont know why it didnt show up in the app drawer initially)

Just realised the SU binary is slightly out of date on this superboot, uploading new version now.
P

Updated with latest SuperSU.
P

time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0

JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
I'm working on one today...

JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve

sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.

sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan

danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Thanks. I will check the partitions info on that and use for build.
I am going to start build now. Will let you know how it goes. I should be getting my ATT One X tomorrow, so I will test (unless there are some brave souls out there...).
Steve

danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Lte toggle = services.jar (/system/framework) & settings.apk (/system/app)
also, deleting TetheringGuard.apk from the AT&T unit will enable the tethering ability.

JSLEnterprises said:
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
Click to expand...
Click to collapse
Thanks. This doesn't look like anything that would affect boot.img, good to know. Hope ATT won't mind if I brick my device tomorrow, lol.

You guys are doing a fantastic job for both Rogers and AT&T users! Thanks!

Great job, guys!
I'm at work and can't install the USB drivers to operate my device in the Bootloader/Fastboot but you can be damned sure that I'm eager to go home and flash this!!! Been waiting so impatiently for root and you guys did the trick. Thanks so much

Unbricked TF101, but no Updates?

Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof

NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.

removed

Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on

If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.

Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof

adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.

Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof

adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.

Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!

Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof

There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.

If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.

Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof

Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip

I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.

Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof

bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof