yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T General] Ashcunak:
Can you check in your cach logs to see what happened and what went wrong?

btw. i had to copy the file out side the cache in order to read them with a text editor/viewer, so i coped them to sdcard/temp/ oddly when i tried to open it via the original folder it looked blank.

/cache/recovery/last_log specifically i think.

my download and copy just finished here, will test soon.

edit: ps someones started a thread on this http://xdaforums.com/showthread.php?t=1853145

should possibly consolidate over there as more people with this issue might see it and help... eh?
[Transformer TF300T General] WIIstpM:
Haha that's what I noticed I opened the log and it was blank I was like "EH. WTF!?"

lol

Anyway I posted my log on the thread you specified.
[Transformer TF300T General] wihe1:
I am new to the forum. I could not see a message from Holland. This evening I checked and found the update.

Downloaded the update and installed it without any problems.

Tablet is in original state, not rooted and not unlocked
[Transformer TF300T General] vap_66:
Well, it seems that "PlusOne.apk" is missing and this got me to that red triangle. Where could I find that file? (I didn't had the file at all)

Trimis de pe ASUS Transformer Pad TF300T
[Transformer TF300T General] Tequila.CZ:
Try here:

http://xdaforums.com/showpost.php?p=30531795&postcount=23

The post says he is missing PlusOne as well, but someone added it.
[Transformer TF300T General] jackastor:
Is there any problem with the US varient vs the ww? I mean Canada Vs US seems to me its preety much the same thing any way.

If not what are the differences?

regards

Jack
[Transformer TF300T General] ch3mn3y:
I think that there are some small differneces because law in us and europe i different.

Sent using SO-01C with DoomKernel v14 (460mHz/1.21gHz)
[Transformer TF300T General] Bolandk:
So far no differences as far as I can tell. Seeing as the user can specify dictionary language (UK/Canadian English vs. US) and other such details, switching between makes little difference. It's unfortunate that Asus won't release the different firmware all at the same time, but I suppose someone needs to be the guinea pig:o

Cheers
[Transformer TF300T General] rickc3k:
My tf300t had originally a CN build and I updated it on the first boot to .30. Then converted to WW. I have waited several days but if I try to look for an update it says there is none. Not rooted or unlocked... Will I ever get it OTA or do I have to wait until the manual file is posted?
[Transformer TF300T General] mikaole:
Think you just have to wait or unlock Bootloader and flash it with TWRP recovery
[Transformer TF300T General] rickykemp:
Or do this http://xdaforums.com/showthread.php?t=1853145
[Transformer TF300T General] maspro:
Still no Jelly Bean on stock non-rooted TF300.

Arrghh, still no update for my TF300, it keeps saying "no update available". I was rooted at first and maybe suspected I changed some system settings through some apps I had installed. So just to be sure I did a clean total reflash (including a factory reset) of the latest ICS firmware (WW_epad-user-9.4.3.30.zip) from the Asus website. So now I'm completely stock, non-rooted and unlocked but still no update available. And it isn't like I had a failed install or something like that, it simply never offered the Jelly Bean firmware.
[Transformer TF300T General] rickc3k:
Thanks, I guess I will try next weekend
[Transformer TF300T General] Grifter357:
TF300T WW rollout to Philippines around 8 hours ago

Hello all,

The Jellybean OTA update was pushed to Philippine users today around 2am Aug 28 local time (GMT +8). I was excited to see the firmware downloading... At last! JellyBean!

I'm using a TF300T rooted but locked, using SuperSU and Voodoo OTA Rootkeeper. One of the reasons I rooted the unit was to use EZOverclock.

The excitement I felt during the firmware download quickly turned into terror after applying the update and restoring root. After the reboot, the device got stuck in an endless bootloop.... :eek:

After desperately trying to troubleshoot the unit for two hours, I finally realized that the EZOverclock app was the cause of the problem. Managed to remove it and sighs in relief when the unit returned to normal (clockspeed as well... :mad:).

Created a thread to warn other WW users about it here:

http://xdaforums.com/showthread.php?t=1856788

---------- Post added at 10:19 AM ---------- Previous post was at 10:12 AM ----------

Try being one of the handful of Motorola Atrix ME860 (Asia version of the Atrix 4G) in the Philippines (where it was not officially released by Mototola Phils, got mine from Hong Kong...)

According to the Motorola website, ICS rollout for our version is "under planning and evaluation". At least the US version has a tentative rollout schedule for Sept 2012....

Also, the only accessories for it available here brand-new are a few Otterbox Commuter cases and the generic USB chargers
[Transformer TF300T General] gab_hamelin:
Was working for me with this method. Thanks.
[Transformer TF300T General] vap_66:
Units with unlocked bootloaders do not receive OTA updates. Wait for Asus to post the file on the website.

Trimis de pe Motorola Defy
[Nexus S Q&A, Help & Troubleshooting] aaps59:
Hi, hope Im not double posting or anything, but I havent found a solution to my problems yet.

I recently purchased Nexus S 4G, thinking it was working, but it is not. It powers up, but doesn't get to the main system. It sticks on the Nexus colorful flashing things and wont get past that. Sometimes it sticks on the Google logo. Is there anything I can check, or somehow restore it or something to get it to boot up? I can also get to the fast boot menu, but when I get there, and try recovery, it just gives me the sad dead Android with his tummy open with a red triangle.
[Nexus S Q&A, Help & Troubleshooting] jayjay3333:
If you can get into fastboot just flash CWM http://www.clockworkmod.com/rommanager and SU http://androidsu.com/superuser/

Put SU on phone SD card

Reboot phone into bootloader mode

Open a command prompt and go to the folder in where CWM is

Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.

fastboot flash recovery recovery-clockwork-touch-6.0.1.0-crespo4g.img

Now go to recovery.

There, using the options, navigate to the install the superuser zip file

Reboot.
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:

/data/cust/app

Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.

Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.

/misc	emmc	/dev/block/mmcblk0p14
/vrcb	emmc	/dev/block/mmcblk0p16
/recovery	emmc	/dev/block/mmcblk0p17
/recovery2	emmc	/dev/block/mmcblk0p18
/boot	emmc	/dev/block/mmcblk0p19
/system	ext4	/dev/block/mmcblk0p20
/cache	ext4	/dev/block/mmcblk0p22
/cust	ext4	/dev/block/mmcblk0p15
/data	ext4	/dev/block/mmcblk0p27
/tmpdata	ext4	/dev/block/mmcblk0p23
/persist	ext4	/dev/block/mmcblk0p21
/tombstones	ext4	/dev/block/mmcblk0p24
/firmware	ext4	/dev/block/mmcblk0p1
[Huawei MediaPad, T-Mobile SpringBoard] drock dj:
Thanks

Many ty's for this.
[Huawei MediaPad, T-Mobile SpringBoard] keno7777:
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
[Huawei MediaPad, T-Mobile SpringBoard] robkaos:
Do I have to do step 11 ?

---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------

Also can I do it without PC?
[Huawei MediaPad, T-Mobile SpringBoard] robkaos:
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.

Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.

Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.

Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.

Not sure what you are asking here...please clarify.
[Huawei MediaPad, T-Mobile SpringBoard] robkaos:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:

http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/

http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar

I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.

If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
[Huawei MediaPad, T-Mobile SpringBoard] cmstlist:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
[Huawei MediaPad, T-Mobile SpringBoard] robkaos:
Thanks for the clarification
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
[Huawei MediaPad, T-Mobile SpringBoard] Bogdan45:
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
[Huawei MediaPad, T-Mobile SpringBoard] knightpawn:
Failed updates and can't recover - PLEASE HELP!

Well, unfortunately, I've messed things up. Here's what happened:

1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3

2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.

3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.

4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.

5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.

Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!

Thanks!
[Huawei MediaPad, T-Mobile SpringBoard] cmstlist:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.

So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:

- stock recovery.img to recovery and recovery2

- boot.img just in case that got buggered up

- cust.img

- system.img.ext4

- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)

At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
[Huawei MediaPad, T-Mobile SpringBoard] knightpawn:
Any particular locations for the other files via fastboot?

Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.

I understand that recovery.img should go to the recovery and recovery2 partitions.

What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)

Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.

With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!

Thanks a ton!

[UPDATE]

So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.

So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
[Huawei MediaPad, T-Mobile SpringBoard] Bogdan45:
CM10 has too many problems, why would you want to use it?
[Huawei MediaPad, T-Mobile SpringBoard] Bogdan45:
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).

I really wanted to switch the apps installation path to the external sd card but did not succeed.
[Huawei MediaPad, T-Mobile SpringBoard] ladyjhova0928:
What am I doing wrong

I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.

Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
[Huawei MediaPad, T-Mobile SpringBoard] kc7gr:
Success!

All right... It took me a while, but I have achieved complete success! My pad is now rooted, yet still maintaining 4G connectivity.

For the benefit of others who may run into the same pitfalls: I followed xdajunkman's process almost to the letter, but ran into a few differences.

1. Regarding Step 7: It appears xdajunkman's luck in getting his tablet to alternate between recovery and recovery2 may be a one-shot. After flashing the CWM loader to recovery, I was unable to get it to come up. Once I flashed it to recovery2, however, it booted immediately.

2. Regarding Step 2: CWM-SuperSU-v0.95.zip has been updated to version 0.96. This is the one I used, and I had no problems with it whatsoever.

3. Regarding Step 11: Since I ended up flashing the CWM loader into both recovery and recovery2, I had to use a different method to restore my T-Mo stock recovery.img files. I went back into fastboot mode and used:

fastboot flash recovery recovery.img

fastboot flash recovery2 recovery.img

My source for recovery.img was the file Springboard-ics-update.zip mentioned by vicfuze in this thread: http://xdaforums.com/showthread.php?t=1831724

The interesting part is going to be what happens when T-Mo sends out their next OTA update. I'm going to be very curious to see if it takes, as well as whether root is still there once it gets done.

UPDATE 24-Oct-12...

I accidentally deleted something I shouldn't have yesterday, so I ended up reflashing the tablet to T-Mo defaults today and then re-rooting it. In the process, I found that copying the CWM loader image to recovery2 is all that was needed to let the thing boot said image.

If you end up doing the same thing, you would also need to slightly alter xdajunkman's instructions in Step 11 as follows.

INSTEAD OF: dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img

USE THIS: dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard2/recovery.img

This will have you working with the recovery2 section as opposed to recovery.

My thanks to ALL who contributed to these efforts!

Happy tweaking.
[Huawei MediaPad, T-Mobile SpringBoard] 415porto:
CWM Mode Fail

When trying to boot into CWM mode it says update fail. Press power button for 10 seconds to reboot. I am using the same exact device that you are using same firmware and everything. Now I have no wireless and I think I ****ed it up help!!!
[Huawei MediaPad, T-Mobile SpringBoard] kc7gr:
Check your steps!

Note my last 'Update' to my earlier post. It's very important you get the CWM image flashed to the right partition (recovery2) for the trick to work. Your symptoms make me think you did what I did at first, and put it into the 'recovery' section.

Remember, you can always flash the unit back to T-mo default and try again, assuming you have the last image file they put out. If you lack said file, drop me a private note.

Happy tweaking.
[Huawei MediaPad, T-Mobile SpringBoard] xdajunkman:
Agreed....if your device is telling you update failed when you try to boot into CWM recovery then it is booting into stock recovery. It seems the best way to make this work is to flash both recovery positions aa described above by kc7gr. Flash both recovery partitions with the CWM image and try again.
[Huawei MediaPad, T-Mobile SpringBoard] 415porto:
Got It!

I flashed recovery and recovery2 but now how do I get updates. I didn't back up my recovery2 partition. Do you have a copy of the OEM recovery 2 partition?
[Huawei MediaPad, T-Mobile SpringBoard] cmstlist:
There's a recovery image inside the TMo ICS update zip. Flash that to both recovery partitions and you'll be on stock recovery.