Hi
Here are the nvflash versions for the .17 update. For those that wanna go back to stock for warrenty or have a dualboot this can come in handy.
I've tested the WW version on my on transformer and it worked (got a B70 with SBK1) created the US and TW version the sameway with the same config files so it should work! LET ME KNOW IF IT WORKS FOR YOU
But remember i'm not responsible for any bricks flashing my causes and you do this on your own riks.
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
I'm hosting them on my own server:
http://www.xdafileserver.nl/
*Added US version, and TW version
Thanks
.
Worked great on a B60 and a B70.
Thank you.
Sent from my Transformer TF101 using Tapatalk
not for TF101G - B90 ?
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Korumera said:
Nopes these are only for versions with SBK1 and the B90 series doesnt have that sorry m8, but there are otherways to get back to stock for B90 just look in the dev section.
Click to expand...
Click to collapse
oow.. thanks for the reply..
mine still in stock, but HC 3.2.1.. i thought ICS for TF101G already available for certain countries..
thanks a lot anyway..
@Korumera
I want to create JP version.
Can you tell me how to create ?
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
rdosti said:
Thanks would this remove any version of clockwork recovery such as the disasterours 5.x that makes you do a cold boot on each restart?
Regards
Click to expand...
Click to collapse
Yes
NVFLASH'ing removes every partition and restores the orignal one.
Windows won't allow me to install the driver. It says the third-party INF does not contain digital signature information, and it doesn't give me an ignore and proceed anyway option. Any ideas? I'm doing this from device manager.
Edit: if anyone else has this happen, rebooting to boot options (the screen that lets you boot into safe mode and such) there is a setting to disable signed drivers. That worked for me.
This is so useful. Thanks.
Really good job! Thanks man!
nicely done! I was thinking about creating one for this version but I got tied up with work.
No problem
Hope it comes in handy!
and chadster214 work comes first at least they say so haha
Hi!
ROM: NVFLASH_ICS_9.2.1.21_WW_NOROOT
CWM Recovery ICS - Stock?
Edit: When i press power+volume down for 7 seconds (aprox) show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Thanks a lot. Fixed a issue for me. No matter what I flashed I couldn't get the wifi to work again. Just stayed in a state of trying to turn on.
Tried and tested the WW version; no problem at all.
Korumera said:
Hmmm try to flash it again, i've checked the zip file and it contains all the files including the recovery (blob.sos)
Click to expand...
Click to collapse
I install the new NVFLASH_ICS_9.2.1.24_WW_NOROOT
My recovery it's the same, how is the recovery stock? you have screens?
I read that is normal in stock (android with admiration sign)
Thanks in advance, sorry for my english
This process works fine. A few things to keep in mind:
1) Unzip the .7z file in a folder in a folder at the root of your hard drive: I typically open my Windows boot drive, create a new folder, name it "nvflash" and dump the archive's contents into it. This avoids getting errors as a result of the Windows folder/file path being too long.
2) Timing is important when connecting the tablet to the computer: on Windows 7, I simply press the power on+volume up buttons for 2-3 seconds (up until the "new hardware found" bubble appears in the tray area), I then let go and make sure the screen remains off (*VERY IMPORTANT*).
3) To install the Windows driver for my TF101, I go to Device Manager, right-click on the APX icon (it should show a yellow exclamation point), update the driver by pointing Windows to the /usbpcdriver folder (e.g. c:\nvflash\usbpcdriver, for example), let Windows finish the install and ONLY then start the flashing process by running download.bat in Administrator mode.
Related
Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts
I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh
Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.
Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan
I did the wrong thing and assumed my phone was still rooted after using t-mobile's upgrade from froyo to gingerbread.
I flashed my phone and now I am stuck on the manual mode screen. I assume (oh boy) I cannot place a custom rom since my phone wasn't rooted and therefore doesn't have permission to write to the phone. (I can't flash bootloaders)
At this point my data on phone is trashed I am sure, but I do have the contents of my sd card intact. I didn't backup before I started - hijole! I know.
I am not sure if I can use Super one click to root and continue to install a custom rom, or I should go back to base line and restore to original. Problem is I don't know how to goto the original at this point, and I don't know if super one click will work with my phone at its current state.... Argh! Will post pic of screen when I go to lunch today... Thought i had it with me on my iPhone. I assume to much!
Can you be more specific on the manual mode screen and what it looks like? Just to clarify, when you flashed from Froyo to GB (using Kies Mini, I assume) you did lose root. However, that does not prevent you from flashing a custom ROM. You can use ODIN or Heimdall to flash a ROM, then use one of those again to flash a kernel with root, with CWM, with voodoo lagfix, all of the above, or use SuperOneClick (the latest) to root it.
I'm guessing you might be able to get into download mode which means you could ODIN RaverX3X's 2.3.6 Stock (http://forum.xda-developers.com/showthread.php?t=1353176) which is the Kies Mini official update just repackaged for ODIN. That will get you onto stock 2.3.6. From there you have options
I am supplying a pic of the "Manual Mode" I was referring to, and yes I did originally use Kies to upgrade from Froyo to GB. Again thanks for the info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it won't show since I am new to this forum
NEVERMIND, found the upload feature in this forum
djlalorocks said:
So it won't show since I am new to this forum
NEVERMIND, found the upload feature in this forum
Click to expand...
Click to collapse
Sweet, so you have it working?
I think he says is stuck on that screen.
Do a battery pull on your device to turn it off, then put it back in. To put it into download mode for odin, hold volume up+down while plugging your phone into your pc. Then use odin to flash.
Sent from my SGH-T959V using XDA App
The problem he initially had is the rainbow screen and, although he can get into download mode, he's been unable to get his computer to see the phone. Thus he couldn't use ODIN to re-flash a good ROM.
djlalorocks, can you verify the state of the phone now? The screenshot you gave, by the way, is the CWM recovery screen. If we can get a good CWM-based ROM onto your SD card then you could flash from there.
Do you have an SD card reader for your computer you can use? I know the phone's not working in mass storage so that option is out.
Edit: My apologies; I went back and re-read what you wrote. When I saw that you found the upload feature I thought you meant you got a ROM to upload to the phone. I didn't realize you meant the picture of the screen. I'm slow sometimes
Haven't had a chance to work on it... I am on a mac, and yes I can place files onto a sd. My windows computer is having usb driver issues.
djlalorocks said:
Haven't had a chance to work on it... I am on a mac, and yes I can place files onto a sd. My windows computer is having usb driver issues.
Click to expand...
Click to collapse
Heimdall (open source alternative to ODIN) works on the MAC, I believe. Regardless, if you can download Raver's Kj6-Rom-CWM-Offical-GB-2.3.6, put it on the SD card, go into the recovery screen (the one where you made the screen shot), use the volume down key to scroll to "install zip from sdcard", press the power button to select it, then select "choose zip from sdcard", scroll to where you put the file mentioned above, select it with the power button, then scroll to "Yes - Install sgs4g-OfficialGB2.3.6.zip" and select it.
Hi, my girlfriend's Transformer is stuck at 8.6.5.13,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried to update via Settings > About Tablet > System Firmware Update > but the "Check Update" button is greyed out.
I have also tried installing 9.2.1.11 via an external Micro SD card, but the card simply mounts. I have unzipped the .zip I downloaded from the ASUS site, this created another .zip file, WW_epad-user-9.2.1.1.11.zip.
If I unzip that file, I get a folder with the same name. Inside that folder is a file called blob and a folder called META-INF with RSA security certificates and another folder.
I suspect I need to update to an older update first, maybe even a few updates before I can jump to ICS. But the ASUS site only has 9.2.1.11.
I have searched extensively, and read quite a few pages of posts. But no joy.
The tablet is completely stock, not rooted and is the B50 variant. I'm not an ANDROID noob, by any stretch of the imagination. But the tablet is my girlfriends, and I have only ever played with the ZTE Blade and currently my LG O2X, running ICS (Thanks owain).
So from the fear of f*****g up my girlfriend's best gift from me. I just thought I would ask some experienced folks here for help.
I hope someone can help. Kind regards. Anil K Solanki
After you unzip the download, you will have WW_epad-user-9.2.1.1.11.zip in a folder ASUS/Update/ or something like that. I think you can try 2 things 1) Try copying the whole ASUS folder and all the contents to the root of your sdcard and then insert it onto the TF. It should find it and ask you if you want to flash or 2) rename the second zip to EP101_SDUPDATE.zip and put it on the root of your sdcard then reboot into recovery. This one might be tricky with windows because I think it is case sensitive or it might try to add a .zip to your .zip.zip. Thanks for nothing windows... Good luck with windows 8.
I think you'll need a stock recovery, but hopefully one of those methods will work so that you don't need to get a new girlfriend.
this worked for me
Go to settings - apps - all - find the DMClient entry, force close, clear cache and restart your TF
the button was not greyed out
gee one said:
After you unzip the download, you will have WW_epad-user-9.2.1.1.11.zip in a folder ASUS/Update/ or something like that. I think you can try 2 things 1) Try copying the whole ASUS folder and all the contents to the root of your sdcard and then insert it onto the TF. It should find it and ask you if you want to flash or 2) rename the second zip to EP101_SDUPDATE.zip and put it on the root of your sdcard then reboot into recovery. This one might be tricky with windows because I think it is case sensitive or it might try to add a .zip to your .zip.zip. Thanks for nothing windows... Good luck with windows 8.
I think you'll need a stock recovery, but hopefully one of those methods will work so that you don't need to get a new girlfriend.
Click to expand...
Click to collapse
ICE Cream Sandwich baby! Option 2 worked. I have never booted the Transformer into Recovery before, so I got to see a great animation of some gears spinning inside an ANDROID robot. Cool.
I have been asking myself, "why the f**k are you bothering with this update?". Susy my girlfriend doesn't care, as long as the tablet continues working. But after 5 mins, I can tell it is a lot faster. Worth staying up until 1.30 am for.
Many thanks. Anil
grinnerD said:
this worked for me
Go to settings - apps - all - find the DMClient entry, force close, clear cache and restart your TF
the button was not greyed out
Click to expand...
Click to collapse
Hi, thanks for taking the time to reply. Thankfully option 2 from "gee one ", sorted me out.
Have fun. Anil
Hi guys,
I made a little tool which you can use to install your favorite recovery-system to the LGO3D.
Here it is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: LG-P920_offline_Recovery-Toolkit_XDA-Edition.zip
md5: 6E3C8CEE5989302C5C333D6491E9373E
Recovery images and instructions are inside the tool.
The version is called "XDA-Edition" because the integrated help links are going directly to this thread.
All credits for the recovery images goes to their developers - LG Electronics or the Clockworkmod-Team - Thanks!!
Have fun!
Greetz paki
Thanks man..
great
doubt
hdk1984 said:
great
Click to expand...
Click to collapse
works on p920h Baseband 20A
Awesome! Thanks!
Please cross-post this to the LG Thrill Forums, it would be much appreciated!
Thanks! It's very useful and simple tool. There is a similar non-GUI tool called Recovery Manager but I can't use it (I am getting messages like "adb server is out of date. killing.../ failed to start daemon" etc). I hope that with your tool, I won't have similar problems.
If CWM is already installed, can I install/flash over it the Stock Recovery or the CWM-Touch? And later, re-flash and go back to CWM?
Hi,
I tested the tool many times before and I've never had problems with a running adb-server.
You can change the recovery sytem as often as you want by replacing the old one.
greetz paki
Hi and thanks for the quick reply. Unfortunately my O3D has a problem with your tool, like with the other similar tool (Recovery Manager).
Some time ago, I installed the CWM-Touch with another tool you've posted here, and now I want to go back to the CWM no-touch version. I just used your new tool trying to flash the CWM, and everything finishes successfully (First I get a window that says "waiting..." and then another one that says "success.. done" or something similar).
But when I reboot to the recovery, I still have the CWM-Touch version. I tried already with your tool 3 times to flash the normal CWM and 2 times the LG stock recovery and even if it says that they flashing went successfully I'm still stuck to the CWM-Touch.
Do you have any idea why my phone is stuck with the CWM-Touch? Could it be a corrupted file somewhere like the Superuser binary (I have the latest version)?
Hi,
maybe your pc-firewall is blocking "adb-win.exe" - please check this!
Please open the windows taskmanager and kill all processes like "adb.exe; adb-win.exe; adb-windows.exe".
After that you can make a new try to flash the stock-recovery.
The Version of SU doesn't matter.
The success message also appears when the operation is canceled due to connection problems.
I know that the tool is not yet perfect, but this is my first attempt at a GUI. I try to eliminate the errors in a next version.
greetz
I works!
Great!
Thanks!
Thanks again for the quick reply. The adb***.exe processes are always killed when I exit the tool and I turn my (default) Win7 firewall temporarily off during the flashing attempt.
I'm almost certain that this is not a problem of your tool but of my phone. Because the same happens when I try to flash any CWM or stock recovery with the other similar tool, the Recovery manager.
Try to reinstall the USB-driver-package - maybe there is the problem?!
http://www.mediafire.com/download.php?eec7g8dekfggwag
USB-debugging is activated?!
greetz
Thanks. Yes, the USB-debugging is on all the time.
I installed the USB-driver-package from the link that is provided when you start the recovery toolkit.
I suppose that the link in the toolkit is the same one you've posted above but I'll uninstall it, reinstall this one and try again.
Yes - it's the same file!
Please use a different USB port of your PC so that the drivers are installed from scratch.
Which Windows-system do you use?
Thanks. I'll better use not only a different USB port but a different PC as well.
All the attempts so far were done from my laptop with Windows 7. My PC has Vista and I also can try it from my second laptop with WinXP.
I'll test it and let you know. Thanks.
OK
If you are using a Windows7/Vista PC with original firewall, then I recommend you this tool. With it you can control the access of programs.
There is a free version that goes for first.
Good luck - greetz paki
YES! It worked!
I installed the LG USB-driver-package on the PC with the Vista, and the CWM no-touch version was installed successfully with the first attempt!
Thanks a lot for your help and your prompt replies!
Grüße
It's my pleasure!
greetz paki
Hello there, took notice of your application here and did a short write up for it on the XDA Portal.
here's the link:
http://www.xda-developers.com/android/tool-for-the-optimus-3d-installs-your-favorite-recovery/
I had written more, but my editor thought it prudent to edit out some of it. regardless, i hope you enjoy it!
PoorCollegeGuy said:
Hello there, took notice of your application here and did a short write up for it on the XDA Portal.....
Click to expand...
Click to collapse
Thank you very much. This is a great honor for me!
Greetz paki
Hi there, I'v tried to update my FT101. So I've found the right website for the job, KatKiss ROM MarshMallow 6.0.1 Release. Got a lot of things going for me so I was really in the mood for it.
I came a long way.... until the moment came to update Android itself. Entered the SD card. No SD card found. Oke let`s try another one, no SD card found. Alright, also found a link on how to install the FT101 with a direct cable from a PC. Plugged in the cable from the FT101 to my win10 pc, no connection what so ever! Oke let`s try my win7 pc, no connection what so ever! Oke let`s try the laptop, no connection what so ever! So now I'm running out of ideas, last and final try. Different SD format's, NTFS, FAT, FAT32 and exFAT (tried it with two different card's).
Made some photo's of my progress, is there anyone that can help me further? Please? :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the OS you were using is still there, try to see if that detects the SD card
AlexS08 said:
If the OS you were using is still there, try to see if that detects the SD card
Click to expand...
Click to collapse
I can't find the OS anywhere. Seems to be gone :crying:
Can't restore the Android version.
Try using a different SD card
Sent from my LGLK430 using Tapatalk
I've tried two different cards. Still no luck.
Are you plugging a microsd card into the microSD card slot?
Sent from my Transformer TF101 using Tapatalk
AlexS08 said:
Are you plugging a microsd card into the microSD card slot?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Well yea, what else am I suppose to do with it?
Any other ideas?
I'm still hoping to fix this but i'm gonne need some help with it
So assuming by your pics, you still are able to get into bootloader/APX AND Recovery (TWRP)... So you are not yet completely bricked, this is good.
Your TWRP version is 2.3xx and you wanted KatKiss 6.0 marshmellow.
You needed the latest TWRP 2.8xx, that was in another thread.
Code:
http://forum.xda-developers.com/showthread.php?t=2434422
If you find a way to get the sdcard reading (only formatting linux ext3/4 or FAT32 will work) or the pc to connect to TWRP/APX, install the newest TWRP and reboot the recovery (important), and try again to install KatKiss 6.0mm AFTER the reboot.
Your original USB cable for the asus is in good shape? Not frayed or busted? This is important if you want to recover back to stock:
(I cant post links yet) Download the Original factory firmware and the ASUS drivers from here
Code:
http://www.asus.com/us/support/Download/28/1/0/1/32/
Those should be able to get you back to factory.
Are you using a one-click method to root and do that stuff? Most of them are outdated nowadays, packing in old cwm or old twrps.
If need arises, you should check in Windows Device Manager and see what the TF101 is showing up as when you connect.
To get the right driver for it working:
connect the USB
boot the TF101 into APX/bootloader and leave it there
delete the device in the DeviceManager (and checkbox the Delete drivers as well)
now boot the recovery of the TF101
On DeviceManger delete the new device (and driver checkbox as well) again
disconnect the USB
install the ASUS driverpackage letting it finish installing
then afterwards reconnect the USB
reboot into APX, and driver should install in device manager, when it appears, then reboot into recovery and wait for it to install a driver.
You should see if any of the tools you had used has in its directory adb.exe and the related dll files, open a command prompt in that folder with the files (hold shift when rightclicking the whitespace inthe folder> Open a Command Prompt from here). Then with TWRP open and USB connected, go to Advanced -> Sideload ABD, see if its connecting something in Windows Device Manager. If it is working, then that means you can use in the command prompt
Code:
abd sideload xxxxxxxx.zip
-----------> xxxxxxxx being the filename you want to flash
repeat the command after each one finished with the rest of the zips you want to flash
Hi ich0,
Thank you so much! I'm going to give it a go, I will let you know what happend