yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] ScottHW:
Inaccurate

Pretty sure that description is not entirely accurate.

I have a locked bootloader, but since I noticed the automatic download of the OTA, I quickly turned off WiFi. Disabling DMClient.apk means that the OTA will not be installed.

Conversely, if you have an unlocked bootloader, you might have manually applied the update. There are numerous descriptions of methods to accomplish this. Hopefully anyone who understands the manual update methods would already understand the implications of the updated (and re-locked) bootloader.

Unfortunately, I know for a fact that more than a few people on these forums have taken the update, either OTA or manually, only to end up disappointed with the new .30 bootloader. AFAIK, there is currently no way to produce the blobs for NVFlash access from the .30 bootloader. And, there is also currently no way to downgrade back to a pre-.30 bootloader.
[Asus Transformer TF700] rikc:
I bought the Infinity under the impression that I could (completely) unlock it if I wanted. Off-course I do my homework before I shell out several hundreds of euros.

Now this makes me sad, like I'm sold something different than what it said on the packaging.

I mean, I haven't unlocked it yet and won't in the coming time... I have two years of waranty during which I'm probably going to stay locked. So the .30 got me blindsided as well... and it's not that I didn't take care. I saved root and am now without an unlock but with root on JB. But still, Asus will not support my Infinity with new software updates as long as custom roms will. And this also severely hinders development of custom roms... So whereas an unlock tool is more or less an opened hand to de community, removing the need for hacking this more or less takes that back.

I hope this challenges someone to try and break Asus' measures :)
[Asus Transformer TF700] jonstrong:
Yup...I'm extremely disappointed as well. After playing with my Galaxy Nexus since December, having flashed ROM's, bootloaders, radios, kernels dozens of times, I was totally psyched at the idea of getting a leading edge tablet from a company like ASUS that actually supported ideas like unlocking - and even made the tool(s) available to the community. My timing was bad, and I didn't do quite enough research to see what I was getting into: after comparing all the tablets out on the market over the last few weeks, I decided on a TF700, brought one home (with dock) fired it up, let the two updates run...and discovered that I lost my option to use a tool like NVFLASH to make all the hobbyist / developer flashing perfectly safe.

I really don't want to return this to Best Buy. I love the tablet, but it feels like much of the motivation I had to get this over an iPad disappeared due to this latest draconian measure put in place by ASUS. I truly hope they reconsider, or somebody in the community figures out how to bypass this latest restriction. Count me in as one very disappointed customer.
[Asus Transformer TF700] paddycr:
This seems to be going nowhere fast unfortunately. Below are my e-mails with Tien. He's a good guy and does his best to support us here in North America. I do believe him when he says ASUS is not trying to profit from bricked bootloaders. However, the main problem seems to be that ASUS HQ are paranoid control freaks :mad:
[Asus Transformer TF700] jonstrong:
Sad and disappointing situation. I've spent the better part of the last year getting to know and enjoy Android with my GNex, and the ability to flash ROMs, kernels, radios, bootloaders, etc has let me tweak it to exactly what I want, knowing I can always fall back to a stock config if needed and start over. SO disappointed to have purchased the TF700, let the updates run, and THEN realize that I've lost the ability to use NVFLASH (never knew it existed before coming here to read up about the TF700).

Love the device, and don't really want to return it. But this is bordering on an iPad kind of experience -- it's pretty and powerful, but my hands are tied. Locked, no root...few options... :crying:
[Asus Transformer TF700] paddycr:
I hear ya. I've got a Nexus 7 and you can do practically anything to those things. I would love the peace of mind of having NVFlash for my TF700. I've got about 10 days left in my 30 day return window to Bestbuy. My current Infinity shipped with .22 and immediately updated to .30. I am sooooo annoyed that I applied that update (the NVFlash thread appeared a day or so later!). I am almost tempted to return this one to Bestbuy. I probably won't cos it's kind of a psycho thing to do but I am quite frustrated :eek:
[Asus Transformer TF700] jonstrong:
Yeah...almost the exact same situation. Only had mine a few days -- probably have close to 3 weeks left to return it to BestBuy, but I agree -- feels like a bad thing to do. Hate to be under the gun to make this decision though. If I keep this one, and ASUS never comes around, I may be stuck with a locked and unrooted TF700 for the long run as far as I understand this.

Also really don't like the prospect of uninstalling 134 apps, scrubbing the internal storage, repacking the whole thing, then taking it back to Best Buy so I can bring home a new one and start all over... arggghhh..... could all be solved if ASUS would simply give us an updated unlocker and NVFLASH...
[Asus Transformer TF700] MartyHulskemper:
+1 -- screw me over once after I make the choice to allow you to, but that second time, nah, too much.

(I was on a custom ROM before .30, so I have Nvflash -- I will still support your movement, however!
[Asus Transformer TF700] jokapo:
+1
[Asus Transformer TF700] Slammin:
I have to say that I don't really understand what the big deal is. I know there is a version of CWM that works with JB and I think TWRP may have been updated to work with JB as well. I unlocked my Infinity the day I got it and have gone from the .26, .30 and OTA JB. I have since tried two other JB ROM's and really don't feel any more limited in the ability to go from ROM to ROM, just as before.

Granted, before the NvFlash tools being made available, I feel my risk of bricking were just as high then as they are now (I don't have nvflash backups), but I also am comfortable enough with this tab to not worry too much about the risks.
[Asus Transformer TF700] jonstrong:
Thanks - exactly what I was wondering, since I've been flashing all sorts of stuff to my GNex without anything comparable to NVFlash to rescue me if I screw up (I guess Odin is out there, but I've never had to look at it). So - if we're careful, selective about what we flash, do we have the option of doing all the standard clean up in custom recovery, e.g., wipe data, cache, Dalvik cache, fix permissions, and reflash as needed? If so...is there any more risk with this device than what I've been dealing with using the GNex for the past 11 months? :confused:
[Asus Transformer TF700] paddycr:
Tien's emails to me (post #30) really say it all - people are bricking their Infinity's and there is currently nothing that can be done about that other than replacing the mainboard at the owners expense. NVFlash access for all users would mean that this could not happen.

I am very glad that you feel comfortable enough that you are never going to brick your Infinity. Clearly there are a large number of people who do not share your views, hence the need for this thread ;)
[Asus Transformer TF700] paddycr:
It's because the ASUS bootloader unlock tool is a half measure. With my Nexus 7, which is fully unlocked, if I screw anything up really badly I can wipe the boot partition and reflash everything. I might be incorrect but it is my understanding that the ASUS unlock tool doesn't allow that - it only allows you to flash the other partitions with things that have not been signed by ASUS.
[Asus Transformer TF700] jonstrong:
Got it - thanks for the explanation, although I'm disappointed at the implications. Think I need to read, learn and wait a bit before deciding what to do...
[Asus Transformer TF700] paddycr:
You're right. I can sort of see where people from like @Slammin say that they cannot see what all of the fuss is about - if you're careful and do your research then your risk of bricking is probably very low even without NVFlash. My thought is that I just cannot account for whatever weirdness that might go on in the future that could make me need NVFlash. Look at the mess some people got into with the new JB bootloader and the old versions of CWM/TWRP. If they had NVFlash they wouldn't be having to send their units off to ASUS to get them fixed for $300.
[Asus Transformer TF700] jonstrong:
Makes sense. Flashing with the GNex got to be a routine for me - many times a week sometimes, and I became complacent. Very easy to get over-confident. I've been lucky - but I got to the point where I stopped checking MD5 checksums after downloading a new ROM or kernel and just went ahead and flashed. Bad practice (probably pretty common though), and exactly the kind of risky behavior that could cause a soft bricking if I started being so nonchalant with the TF700T also.

I do wish I had NVFlash for this - would be a nice insurance policy to keep in the background. Until then, I'll be much more cautious, will read and observe, etc.
[Asus Transformer TF700] Slammin:
Don't get me wrong, I don't like the fact that I've lost a safety net and I really cannot understand the reason for Asus's change in direction regarding, but as far as I can tell, the majority of folks that think they are bricked, actually may not be. It seems that everyone that Pratorian80 has invited to IRC was able to 'un-brick' with his help. I've even had a few scary moments myself :)

I'm hoping this change by Asus is temporary.
[Asus Transformer TF700] ScottHW:
Respond to Asus

Is there much more we can do to encourage Asus to be more mod supportive? I hardly feel like spamming Tien would do the trick, and that is frankly just kind of rude within the XDA community.

Petition? Posting on the Asus FB page? Is there some formal Comments submission page?
[Asus Transformer TF700] jonstrong:
I hope some approach works. Too late for me to think of NVflash, so I feel like I'm in limbo. Looking forward to various ROMs and kernels on this, but hesitating since I won't have the NVflash safety net. Really at a loss right now...:confused:

Swyped from my ASUS TF700T...
[Asus Transformer TF700] scientist343:
I managed to get my nvflash backup before I took the .30 update but I defiantly wish that the bootloader was unlocked fully and the nvflash worked on the newer bootloaders.
[Asus Transformer TF700] buhohitr:
So far the only thing that NVflash is a great rescue, when people did some crazy thing like flash tf300 on tf700. However, most of the brick cases for tf700, nvflash is useless since your pc couldn't communicate with your tf700. The only solution is send it out for a mainboard replacement. So you still need to be very careful when playing with the device. nvflash is NOT a magic bullet that could fix anything you throw at.
[Asus Transformer TF700] paddycr:
Maybe I am missing something here but don't you need to be in APX mode to get NVFlash to work? To run the NVFlash backup process you need to have the APX drivers running successfully. All of the hard bricks on this forum have access to APX mode only meaning they could recover if they had NVFlash. I have not seen one instance where a user has successfully run through the NVFlash process and not been able to recover.

Having said that you are right, NVFlash is not helpful in all situations. If you take your Infinity in the bath with you might not be able to use it to get it working again :D
[Asus Transformer TF700] Pretoriano80:
No offense mate, but can you stop from spreading nonsense like this all over the forum?NvFlash is useless only to those that updated their bootloader at any other version higher than 9.4.5.26 and for those that are still on 9.4.5.26 bootloader but already bricked their device.

Otherwise, once you made good use of the NvFlash tool and saved the backup files in a safe place, you can update to any firmware and bootloader you want and if you brick your device, don't worry, APX mode will be always available so you can use NvFlash to recover your device even from a very nasty brick (i.e bootloader failure).

Anyway, consider NvFlash as your device assurance,but use it wisely and only when is really needed and no other unbrick options are available (i. e. no more recovery or fastboot mode available).
[Asus Transformer TF700] jonstrong:
I've been catching up with all the background / info / tutorial threads in this sub-forum, and appreciate all the time and effort you and others have put in here. I'm spoiled with the simplicity and ease of flashing / modding the Galaxy Nexus (my phone - flashing / changing a couple of times a week, sometimes a couple of times a day over the last several months), with incredibly little risk. I've been reading what I have time to read each night here, and am still working on sifting out fact from urban legend re: the TF700T.

I picked up my TF700T a few days ago, and made the mistake of allowing the two OTA updates before I learned about NVFlash, and the challenges in unlocking / rooting after these updates. Seems that I have a couple of decisions to make at this point:

- do I exercise my option at Best Buy to return this, and start over with a new one, creating the files to support NVFlash? (and if I do this, I'll have to map out what I need to do when I first turn on the new device so I can avoid the OTA updates until I've done what's needed)

- If I keep this unit, will the ASUS unlock tool work on JB even though ASUS states it's for ICS only? I've seen conflicting posts on this question, and I'm not confident I knew the definitive answer to this one. Is it iffy to use this with JB installed? Risky?

- with the Galaxy Nexus, I've only replaced the bootloader once, when moving to JB. Yet I've flashed ROMS, radios, kernels many times. If the tablet is rooted, yet unlocked (is this in fact possible?), is it possible to flash new ROMs and kernels? Or is it absolutely necessary to be unlocked if I want to flash ROMs and kernels?

- if I were to keep this unit, I know that NVFlash (unless ASUS changes their mind) is no longer an option. While it's nice to have a failsafe (98% failsafe?) tool to fix mistakes, I've been flashing firmware on phones and various other devices for many years - and have yet to screw anything up by mistake. I don't flash kernels and ROMs until I see that many others have checked them out and they've been demonstrated to be "safe" and I tend to be extremely careful with any new procedures and firmware. If I were to stick with this approach on the TF700T, how reasonable is it to keep this current device with no NVFlash option and still plan to flash ROMs and kernels?

I realize these topics have been addressed before, but as I mentioned above, I'm trying to distinguish fact from opinion and myth, and trying to get a coherent and concise picture of my options, risks and opportunities so I can make a few informed decisions about moving forward.

Thanks in advance for any clarity on all this.

Jon
[Asus Transformer TF700] _that:
The concensus seems to be that the unlock tool works on JB.

Rooting is possible without unlocking as long as you are running ICS (and it's rather simple).

The locked bootloader does not allow flashing or booting of unsigned kernels or recoveries.

In theory, you should be safe - since the bootloader does not allow itself to be overwritten any longer since 9.4.5.30, you should always be able to get into fastboot mode and repair everything else. In practice, there have been frighteningly many reports of bricks.

(I am still on 9.4.5.26, locked, rooted)
[Asus Transformer TF700] danger-rat:
So, I have a couple of questions...

I plan to pick up an Infinity in the next week or so, and have been doing my usual research, which usually leads me to questions:

1- What are the chances of still being able to buy an Infinity with the .26 firmware? ...or do they all appear to be leaving the stores with the latest firmware version?

2 - Can the firmware version be checked from a booted device (in About Tablet?), because I can see some stores having issues if I have to boot into the bootloader to check the firmware version?

Thanks for your help... dr
[Asus Transformer TF700] _that:
I assume they leave the factory with the latest firmware. So if you buy at a store that has them in stock, chances for an older firmware should still be good. But that's just a wild guess.

Yes, the firmware version is visible under Settings -> About Tablet -> Build Number
[Asus Transformer TF700] danger-rat:
Thanks much!
[Asus Transformer TF700] tbtaf:
I got my tablet from Best Buy, upgraded to .30 like a dummy, took it back and got an exchange to get back to a tablet at .26. I also price match to a website and got it for $347. I must say, I love Best Buy. But either way, when you buy a new tablet, it will be at whatever bootloader was out when it was produced. Original ones were on .22 (I think) as opposed to .26.
[Asus Transformer TF700] lartomar2002:
I would be curious to know where you saw the TF700 for $347. The only tegra 3 tablet I know with the same screen resolution is the Acer a700 and it is selling at that price. You either got lucky and got a non-informed sell person that was not paying attention or you are mistaken on the $347 price. If you are not please let me know where you saw the infinity for that price so I can send mine back to Amazon for a refund and buy that one.
[Asus Transformer TF700] paddycr:
I saw another thread about that a while ago. The site where this price comes from is basically a joke. Someone said that they went into Best Buy, showed them the site and asked them to price match it. Best Buy told them to gtfo :D
[Asus Transformer TF700] lartomar2002:
Thanks, I took hought it was for real and I had paid more than I should have.
[Asus Transformer TF700] drherron:
While still locked I fully support the concept of paying for something means its yours to trash however you like. If I had wanted something that the manufacturer had their hands in after purchase I would have gotten an Apple product I cannot support these types of restrictions going forward.
[Asus Transformer TF700] EpicLPer:
I hate it that they updated my tablet to JB while I let it at a shop to repair my greenscreened broken camera module... I hate them so much for this and the funny thing is that I SAID they should not update... Well, sucks now.

I think that Asus won't remove the lockcode in future updates. They want the money for bricked devices and as I heard to repair a bricked TF201 you nearly have to pay about 400€ right? So nearly a fully new one...

Hope that there's somehow an option to knock the code out and use it again like they did on the Windows RT tablet to run normal ARM based applications on it ;)
[Asus  Eee Pad Transformer Prime] biggem001:
first of all, reposting on multiple forums will get you ignored by most peole

secondly, your statement is extremely hard to read, i suggest you don't speak english.

lastly, we need more information. are you getting errors in the install? is this the first time you're flashing? what rom did you flash that started the issue?

-what you can try now-

Try flashing a rom with TWRP instead of CWM, i've seen issues with CWM that TWRP doesn't have. (http://xdaforums.com/showthread.php?t=1615990)

Use NVFLASH to flash your backed up files. If you didn't backup with NVFLASH prior to all this work then, sir, you should not be flashing in the first place and maybe this is the lesson you need.
[Asus  Eee Pad Transformer Prime] miguelgr7:
ok sorry friend but my english is not good, I commented that when installing a rom gives me no problems, the installation ends well and seems to install something, when I asked to restart the tablet back to the recovery ..
[Asus  Eee Pad Transformer Prime] miguelgr7:
how install the TWRP as if I have no operating system?
[Asus  Eee Pad Transformer Prime] craigacgomez:
This is a development forum... please use Q&A or General for help...

In any case, follow option 1A here http://xdaforums.com/showthread.php?t=1514088
[Asus  Eee Pad Transformer Prime] johnnyutah22:
Agree with Diamondback, this happened to me. This usually happens when you boot into recovery from ROM Manager rather than a cold boot. For some reason rebooting through ROM Manager sets some flags which prevents reboot.
[Galaxy S III Q&A, Help & Troubleshooting] lukecz:
Hi, I´ve enabled in Samsung Dive call and message forwarding. Now i have new SIM card and I can't disable forwarding in Samsung Dive (I don't have old SIM card). I can disable call forwarding in stock calling app, but in text messaging stock app there is no option to disable forwarding. Is there any way how to disable SMS auto forwarding? Stock rom, rooted. Thank you.
[HTC One S] scufutz:
I notice that when i turn on my screen all my notifications pops up with wifi on

Can someone tell if its a bug or an htc setting wifi policies ?

Thx

Ps: its quite annoying
[HTC One S] dc211:
Are you using CM10 or AOKP? Are you using the radio from the 2.21 or 2.31 updates which would be 1.06 or 1.06es?
[HTC One S] scufutz:
I am on aokp with radio 1.es !
[HTC One S] dc211:
With CM10 or AOKP there is no data connection when the screen turns off with the 1.06 or 1.06es radios. They is why you get your notifications when you turn your screen on and why you have bad battery life.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] expeacer:
I made a simple CWM installer to install .587 ROM to XMP.

Official 4.1.B.0.587​

It's work in locked/unlocked bootloader too!​

ES Vodafone source - thanks for the idea to sur1k

Vodafone's apps and customization removed, but any other apps and bloatware not - stock ROM, not cooked.

Rooted, SuperSU app installed

Install instructions:

0.) Copy the downloaded update_XMP587-ExPeacer.zip to your SD card

1.) Install CWM to your ROM

2.) Restart, and enter CWM

3.) If your bootloader LOCKED: mount&storage -> format /system.

4.) Back -> advanced -> Wipe Dalvik Cache.

5.) Back -> install zip from sdcard. Choose the update zip, then follow the instructions.

6.) When it finished, turn off the device.

7.) Copy the downloaded SK17i_4.1.B.0.587_Kernel-Baseband.zip to the Flashtool/firmwares folder.

8.) Start the Flashtool, go to Flashmode. Choose the SK17i 4.1.B.0.587 Kernel-Baseband line, then install it.

9.) If finished, start the device.

+1.) After the first boot, reboot the device again!
​

If you update from GB, at the 3rd step, choose format /data too!!

If you update from .431, in this way, you can keep your apps and settings!

Pics:

Downloads:

update_XMP587

SK17i 4.1.B.0.587 Kernel-Baseband​
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Allen Hu:
Long time no see expeacer:)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] MoonBlade:
Clean !

Great :D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] whalesplaho:
Gracias brov..........!
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] sur1k:
expeacer,

since .587 for xmp is out could we hope for exMIUI update? :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] podoness:
noob question i have baseband 72 using mesa 1.8 kernel.. whats the difference with baseband 77? am using xmp.. thank you..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] whalesplaho:
Didn't even use 72 BB, prefer 64 BB cos its more smoother but seems 77 BB ιş better also... Am on 77 BB & my phone runs fine!!!
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ekakribo:
This is what I'm waitin for
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] thepoky:
great bro thanks!!! downloading..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] masoudr:
what is difference between this and normal ftf ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] saeed-constantine:
sombody upload semcdeskclock.apk from this rom for me?

plz..thanx
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mobilephone01:
I tried it twice but I can't keep root.

I did it follow your instraction.