Related
Reading the boards I've noticed quite a few people who have possibly bricked their phones by using this horrendous piece of garbage. Leave it to LG. Regardless, I would strongly recommend against using it and either waiting for an OTA update or using xboarder's flashable, rooted update here: http://forum.xda-developers.com/showthread.php?t=1179748 .
As far as I can tell, no one has been able to fix the s/w updater issue, which is leaving phones either with no recovery or unable to boot past recovery/restore ROMs.
This isn't the first time either. Just google "LG Software update bricking phones".
Oh wait, I did: http://www.google.com/search?source...gc.r_pw.&fp=79f73547dc11dcbf&biw=1366&bih=667
For those of you who possibly bricked your phones; hang on, I'm sure some of the great minds on this board will come up with a fix. Unfortunately, I'm not one of them.
ALSO! For those of you who don't know this already -- you MUST restore the stock recovery BEFORE trying to upgrade. That's also been causing problems. Just use NVFlash to restore the stock recovery, THEN upgrade using LG software if you must.
The stock camera app doesn't focus as quickly or have nearly as good quality (unacceptable quality IMO) as the LG app. I use my camera frequently and would not have updated if I knew it would be gone (reason why I didn't flash CM7).
Does anyone know of a way to restore to stock? I installed Nvflash at one point or another...
I was stock rooted and update killed that. No more root. But phone works great so far.
Sent from my LG-P999 using XDA Premium App
Update: I was able to restore Clockwork Mod (or had it from before, didnt check) with NVFlash. Then restored one of my NANDroid backups from before.
Bye bye ****ty LG gingerbread update.
I will agree with you. My phone is now bricked. Stuck on the S/W screen with no sign of ever getting it back. I was stock non rooted. And yes I did it on a win 7 64bit machine. Damn you LG and your ****ty updater.
MuzzRock said:
I will agree with you. My phone is now bricked. Stuck on the S/W screen with no sign of ever getting it back. I was stock non rooted. And yes I did it on a win 7 64bit machine. Damn you LG and your ****ty updater.
Click to expand...
Click to collapse
It come back, I brick it the same way, once's before, if you didn't root, hold the power button and volume up at the same time, or if you did root, uses NVflash or clockwork to recover. And don't recommend using a 64bit OS for any type of programming or flashing, just install VMware player, it uses your CPU virtualization to run a different OS, while in your host OS and it's free, that allow you to run XP on a virtual partition, and use USB devies from host machine. The nice thing is if you mess something up, it won't effect the rest of the machine, and you can run the 32bit XP version of the tool.
Works great on mine. I backed up, used tga gunmans stock restore, replaced with stock recovery, unrooted using super one click. rebooted, installed the update, reflashed to custom recovery with tga gunmans app and installed the rooted version from xboarder56. Time consuming would be my only complaint and I love screwing with this thing so who cares.
Yes, my phone is too bricked by this app. Did any of you that are now bricked get to 4% after the download and during the update process, then windows popped up a dialog and claimed the app was no longer responding? this is what happened to me and boom, now i can't get back. I even tried doing the nandroid restore of the stock rom from CWM. Still can't get out of the S/W updater screen. Is there anyway to reflash the bootloader? I did try a live chat with a LG tech and he wanted me to do a hard reset. which is basicly holding down the vol-down and power button. so i did a nvflash back to stock recovery and tried it. It showed the box and android screen but then rebooted back to the S/W updater screen. So I called Tmobile and they won't do a replacement since i used LG's app. Said I HAD to go through LG to either fix or replace the phone. Called LG and have a RA# to send it in. Unfortunatly I have to pay for shipping there and it could take about a week to get it back. This really blows.
MuzzRock said:
I will agree with you. My phone is now bricked. Stuck on the S/W screen with no sign of ever getting it back. I was stock non rooted. And yes I did it on a win 7 64bit machine. Damn you LG and your ****ty updater.
Click to expand...
Click to collapse
Mine worked fine on a 64bit windows 7 machine. I have not had no issues at all. The update is great (I think). The only problem I have is that the camera on the update sucks.
Here's an APK for the stock camera, but I haven't tried it on the update yet because I'm waiting for my phone to restore. Feel free to be a guinea pig
http://www.mediafire.com/?p9aiay5zofq5c1m
pvtodorov said:
The stock camera app doesn't focus as quickly or have nearly as good quality (unacceptable quality IMO) as the LG app. I use my camera frequently and would not have updated if I knew it would be gone (reason why I didn't flash CM7).
Does anyone know of a way to restore to stock? I installed Nvflash at one point or another...
Click to expand...
Click to collapse
maybe you should have waited all of 30 minutes from when it came out for someone to say that it was the vanilla android camera app? either way, just flash your recovery again and just restore a stock nandroid...
I didnt have any problems on win7 64bit installing via the update tool... follow the freaking directions and stop getting so antsy and messing with things... mine was stuck on the S/W screen for a bit but all i had to do was unplug pull the battery and put it back in and plug back in and the update kept going...
deanp0219 said:
Here's an APK for the stock camera, but I haven't tried it on the update yet because I'm waiting for my phone to restore. Feel free to be a guinea pig
http://www.mediafire.com/?p9aiay5zofq5c1m
Click to expand...
Click to collapse
stock camera does not work. try it already. thanks though.
i tried the LG updater on my win7 machine. let it sit @ 5% for 48mins.
then i tried the KDZ on the win7 machine, it crashed.
got out an old laptop w/ winXP SP3 - tried the KDZ method a few times, the final time it gave me model dll msg not found error 100 times, after that it rebooted the phone into gingerbread.
do it the KDZ method on a winxp computer before you mail these phones! i tried for 2 hrs and finally got it working!
edit: my phone was rooted & stock (no nvflash installed)
JHaste said:
maybe you should have waited all of 30 minutes from when it came out for someone to say that it was the vanilla android camera app? either way, just flash your recovery again and just restore a stock nandroid...
I didnt have any problems on win7 64bit installing via the update tool... follow the freaking directions and stop getting so antsy and messing with things... mine was stuck on the S/W screen for a bit but all i had to do was unplug pull the battery and put it back in and plug back in and the update kept going...
Click to expand...
Click to collapse
just because you had no issues doesn't mean others aren't. relax dude. i'm very adept at upgrading/modifying,recovering what seem to be bricked phones. much experience with haykuro's 1.33 death spl. but my win 7 64 bit machine would not install the update. NO MATTER HOW MANY TIMES I UNPLUGGED ETC. it was stuck on s/w upgrade. i nvflashed recoveries,did nandroid backups. tried everything i know of. different cables/ports....nothing worked. until i installed xp on a spare partition. finally kdx worked on the first try,even after the lg update tool failed on xp.
No one has bricked their phones. NVFlash and your back to life. Mine wouldn't even power on... No display... No boot logo... Nothing.
NVFlash and your good.
Asus Transformer 3.1 pwnd
www.MiiWiiChat.com
www.SnapSiteAdmins.com
player911 said:
No one has bricked their phones. NVFlash and your back to life. Mine wouldn't even power on... No display... No boot logo... Nothing.
NVFlash and your good.
Asus Transformer 3.1 pwnd
www.MiiWiiChat.com
www.SnapSiteAdmins.com
Click to expand...
Click to collapse
my point exactly... nobody really understands what bricking is... the definition of a brick means its literally nothing more than a paperweight... it is IMPOSSIBLE do anything to get it to work because the phone will not respond to anything... the fact that its on the S/W screen means it has life yet and as already pointed out just use NVFlash to breathe life into it...
Mine worked fine on the update with XP Pro
JHaste said:
my point exactly... nobody really understands what bricking is... the definition of a brick means its literally nothing more than a paperweight... it is IMPOSSIBLE do anything to get it to work because the phone will not respond to anything... the fact that its on the S/W screen means it has life yet and as already pointed out just use NVFlash to breathe life into it...
Click to expand...
Click to collapse
How? I have NV flasher and tried to flash to stock and it still sits on the s/w update screen. Please if you know what to do, feel free to pm me or respond here. I am at a loss as to what to do.
chrisdepew said:
How? I have NV flasher and tried to flash to stock and it still sits on the s/w update screen. Please if you know what to do, feel free to pm me or respond here. I am at a loss as to what to do.
Click to expand...
Click to collapse
Take your sd card and hook it to your computer. Create a folder named "clockworkmod". Open that folder and create a folder named "backup". Place TGA Gunman's stock recovery in the folder.On your phone hold down the volume down and start button at the same time. You will then see a new screen, release the buttons. Go to "backup and restore". You navigate using the volume up and down buttons and select with the power button. Choose the back up that you will see there. When it is finished navigate back and choose "wipe data-factory reset". Reboot. Power on and you are back to the day you purchased it. Or download a ROM from the developers section. I liked "Ultimate ROM". Then choose "install zip from sdcard. You are now better than when you purchased it.
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
nonstop14 said:
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
Click to expand...
Click to collapse
http://support.asus.com/Download.as...&m=ASUS Transformer Pad Infinity TF700T&os=32
Steps of Update:
1. Check SW version of your Eee Pad Transformer Infinity TF700T*
2. Download Eee Pad Transformer Infinity TF700T Firmware: V10.4.4.16 Only for US SKU and Update version of SOP (From “Manual” Item)
※Firmware update cannot do *SKU conversion* and downgrade version.
Wrong SKU may cause update failure, You can only update your SW version on the Same SKU
*How to check SW version of your Eee Pad Transformer Infinity TF700T?
Path: [Settings]-->[About tablet]-->Build number
Example: You should be able to see the build number WW_epad-10.X.X.X_2012xxxx, where “WW” means SKU.
**Basically download the US update (Guessing since your profile says Detroit you have US version), and store the update onto your micro SD card. Then plug the micro SD into the tab and it should prompt to update. Good luck.**
Are you rooted? Do you plan to unlock? What version are you on? (.26, .30) If you are on .26, check out the thread on NVFlash in development. After you upgrade, you cannot use NVFlash. If you need to upgrade, and don't want to unlock, you should be able to go to asus direct and download the update. Check out this thread on NVFlash : http://forum.xda-developers.com/showthread.php?t=1901479.
Try this one for update: http://forum.xda-developers.com/showthread.php?t=1803090, note, it does require root.
I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update.
I just received my tf700 on Tuesday (from NewEgg) . I got two OTAs updates that afternoon - neither was JB. Finally JB came through last night. So you might have to wait a day or two. ...
Sent from my NookColor using xda premium
Try registering your new tablet on the Asus website.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
junrider said:
I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update.
Click to expand...
Click to collapse
This works perfectly.
Sent from my SPH-D710 using xda app-developers app
nonstop14 said:
I've searched but every thread dealing with this concerns a tablet whose update failed or rooted or something. I just bought my gf a brand new Champaign tf700, it came with ics obviously, and it says no update found when I go into settings and search for update. Tried a factory reset and cold boot... no luck finding a JB update.
How do I get this thing to update? Any easy solutions?
Click to expand...
Click to collapse
1. When still on .26, install Nvflash. Look it up on the forum for the steps. It's not that hard.
2. You might be one of the people having an Infinity that apprarently is not showing up in ASUS' serial number database. This will preclude you from a) receiving an OTA (Over-The-Air) update like the one you're hunting for, and b) will prevent you from being able to unlock the device, so no custom recoveries (and therefore no backups) and no custom ROM'ing. For a lot of us, that was enough to seek (warranty) replacement.
3. If you decide to keep this 700, the procedures given for manually updating a firmware work. However, I'd sincerely recommend you reading through their main threads to really get a good feel for what to do and, more importantly, what NOT to do. There are quite few ways of updating a 700 by hand, depending on what works and your skill level.
Thanks for posting this question. I was having the same issue and now i found my answer WIN!
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.
jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!
jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.
MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...
okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.
Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.
ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!
opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.
Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
maxvsmith said:
Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do:
1. Install fastboot and adb drivers on your PC. You can find instructions for that here: http://androidteen.com/setup-adb-and-fastboot-driver-with-android-sdk/
2. Reboot your Xoom into bootloader mode. To do that, turn your Xoom off. Then, power it back on. Once you see the Motorola logo, count to three at a reasonable speed and press volume down. At the upper left of the screen, you'll see some text. Press volume down until you see "fastboot mode" and press volume up.
3. Connect the Xoom to your PC via USB.
4. At a command prompt, type "fastboot devices". You should see your device listed. If you don't, then the drivers aren't installed correctly.
5. Type "fastboot oem unlock" and follow the on-screen instructions on your Xoom to unlock your bootloader. If the bootloader is already unlocked (since it's an engineering device), you will get a message in your command prompt window telling you as much. Unlocking your bootloader will wipe all data from the tablet so make sure you back up any photos, documents, music, etc. that you want before you do this!!
6. If the bootloader did need to be unlocked, it will reboot after the unlock is done. Once it reboots, perform step 2 again to get the bootloader back into fastboot mode.
7. Go to http://www.randomphantasmagoria.com/firmware/xoom/tervigon and click the link for "images" in the first row of the table (for Android 3.0.1, build HWI69). Download that file, then unzip them somewhere on your PC.
8. Go back to your command prompt and go into whatever directory you unzipped the files into.
9. Type the following commands, in order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
10. Optionally, if you want to re-lock the bootloader (unless you're going to run a custom ROM at some point, I recommend this for security purposes), type "fastboot oem lock". Follow the on-screen instructions to re-lock the bootloader. At the end of the lock process, the Xoom will reboot. Let it boot up.
11. If you choose to leave your bootloader unlocked, just type "fastboot reboot" and you'll boot up.
12. The Xoom will now boot into stock Android 3.0.1. At that point, you'll get eight separate over-the-air updates that will eventually get you all the way up to Android 4.1.2/Jelly Bean, build JZO54K.
13. Once you get the Xoom updated all the way to JZO54K, I'd do a factory reset again just to make sure everything is clear and you're starting anew.
At that point, you should be good to go. Let me know if you have any trouble.
oldblue910 said:
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do
Click to expand...
Click to collapse
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders. I already did unlock the boot loader and installed recovery and tried a bunch of roms and I'm running CM 10.1 I was nervous of trying it at first but after realizing even if it's an engineering and testing tablet it's still the MZ604 and it should be similar to the others in terms of rooting and unlocking the bootloader. And fortunately I was right.
It actually came with really cool apps that I've never seen before too. I wish I backed those up before I factory reset. I tried factory resetting it initially but I lost a few of the apps and special things and it went to a Honeycomb 3.0 I believe. The one before the SD card support.
But I'm loving this xoom now that it's on CM 10.1 and using Jellybean 4.2. Even though it's tegra 2 and not as fast as my TF300T and other tablets out there the unique design, the placement for the ports and the accessories like the HD Dock make this a very unique tablet. It was never one I intended to buy so it was really cool getting it for free. My friend has one just like mine and he's not into hacking, rooting, and customization so I might be able to get the special apps and stuff that was on it from him. But even though I've never unlocked a boot loader once I figured out how to use command prompt it was really easy to do. Thank god for youtube.
maxvsmith said:
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders.....
Click to expand...
Click to collapse
The Verizon XOOM's (MZ600/MZ602) boot loader was not locked any differently than any other Xoom (example Wifi MZ604). It is/was unlockable out of the box, and Moto had the directions on their web site.
Funny, if it says Verizon on the front, I would not expect it to be a MZ604 model, unless the previous owner flashed the Wifi only Xoom (MZ604) firmware/software onto it. Does that bar code label on its back have a model or MEID on it?