Related
Hi. I have a desire s I got s-off using xtc clip the phone has 2.3.3 pre installed I'm trying to root the phone I've read the guides here and tried 'superoneclick' and gingerbreak don't seem to work I don't want to install custom Rom just root the phone anyone got any 99% foolproof method of doing this with minimal loss an brain use! Thanks
Sent from my HTC Desire S using xda premium
There are various links in my signature, they should all help.
Install the adb link by extracting it to PC and the install the HTC drivers then follow the last link flash Cwm and su which will install you a custom recovery and root your device
Swyped from my Desire S using XDA Premium
Thanks. I have adb installed on pc from when I rooted an old wildfire s
Sent from my HTC Desire S using xda premium
jammy2015 said:
Thanks. I have adb installed on pc from when I rooted an old wildfire s
Click to expand...
Click to collapse
Great, let me know how you get on? or have any doubt...the only real danger is if you select the wrong recovery (you obviously need the DESIRE S one (saga)).
hiya. i did what it says here
To root:
Copy su-3.0-efgh-signed.zip to your sdcard root
Start clockworkmod recovery (instructions below)
Select "install zip from sdcard"
Then select "Choose zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back
Then reboot.
You're rooted!
i put the zip on to the sd card waited for phone it wouldnt let me go into recovery so it did its thing i selected 'reflash' an it said it couldnt open pg88diag.nbh which was a file that was placed on there when i did s-off using xtc clip i didnt have any other options to locate the 'su-3.0-efgh-signed.zip'
what am i doing wrong?
thanks
jammy2015 said:
hiya. i did what it says here
To root:
Copy su-3.0-efgh-signed.zip to your sdcard root
Start clockworkmod recovery (instructions below)
Select "install zip from sdcard"
Then select "Choose zip from sdcard"
Then select "su-3.0-efgh-signed.zip"
Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
Then go back
Then reboot.
You're rooted!
i put the zip on to the sd card waited for phone it wouldnt let me go into recovery so it did its thing i selected 'reflash' an it said it couldnt open pg88diag.nbh which was a file that was placed on there when i did s-off using xtc clip i didnt have any other options to locate the 'su-3.0-efgh-signed.zip'
what am i doing wrong?
thanks
Click to expand...
Click to collapse
Not sure what you're doing wrong.
So I'd suggest that you move any PG* files or any existing ZIP files from the root of the SD card (either rename them or move them into a new folder)
I'd also suggest that change these setting on your phone
Settings->Power->Fastboot = OFF
Settings->Applications->Development->USB debugging = ON
Then follow these steps:
Power Off device
Holding down Volume Down, press the Power button to power on Phone (which should take you into white HBOOT screen) with skateboarding Androids!
Using volume down to move cursor down onto RECOVERY
Press Power button, which should reboot phone into CWM (recovery)
Then re-try the instructions that you've shown above to flash ZIP to get root
Report back...good luck
thanks.
one step further now due to turning fastboot off!
now it says ' failed to <something> vairify signature....aborted
I used Revolutionary to initially S-Off and then root my DS. I used it again after I installed a stock ROM and lost ROOT
It's just another way to go.
jammy2015 said:
thanks.
one step further now due to turning fastboot off!
now it says ' failed to <something> vairify signature....aborted
Click to expand...
Click to collapse
Just so that I'm 100% clear:
You successfully performed this command fastboot flash recovery recovery_name.img? (obviously substituting your file name for recovery_name.img)
Are you getting from HBOOT into CWM? and CWM appears to be functioning ok?
Is it on attempting the flash the SU ZIP file that you're getting this message or before?
You successfully performed this command fastboot flash recovery recovery_name.img? (obviously substituting your file name for recovery_name.img)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
have not done the above (dont quite understand it)
Is it on attempting the flash the SU ZIP file that you're getting this message or before?
^^^^^^^^^^^
its when i attempt to flash the su zip file i got that message
thanks for your help
jammy2015 said:
You successfully performed this command fastboot flash recovery recovery_name.img? (obviously substituting your file name for recovery_name.img)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
have not done the above (dont quite understand it)
Is it on attempting the flash the SU ZIP file that you're getting this message or before?
^^^^^^^^^^^
its when i attempt to flash the su zip file i got that message
thanks for your help
Click to expand...
Click to collapse
Ahh..Do you have CWM (custom recovery) installed?
The command that you didn't understand would installed CWM custom recovery for you.
If you don't have CWM custom recovery what are you using to flash the Su ZIP file with?
My previous instructions contained the following steps, which if you didn't follow correctly could be reason why you are having issues now:
You first need to download CWM recovery image file for this device to your PC.
Put the phone in Fastboot USB mode (by following instructions below
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts
Then run a CMD shell from the PC and then issue the commands into it from the directory where you have put the downloaded img file.
fastboot flash recovery cwm-4.0.1.4-saga.img
adb reboot recovery
and then re-attempt to flash the SU zip file.
Then run a CMD shell from the PC and then issue the commands into it from the directory where you have put the downloaded img file
^^^^
thats what i dont understand how to do
i was looking about here on forum and found 'android flasher' i was wondering if that would do the job cos i dont know about cmd shell
heres the link for 'android flasher' http://forum.xda-developers.com/showthread.php?t=794638
thanks again dude sorry if im a pain in the a...
jammy2015 said:
Then run a CMD shell from the PC and then issue the commands into it from the directory where you have put the downloaded img file
^^^^
thats what i dont understand how to do
i was looking about here on forum and found 'android flasher' i was wondering if that would do the job cos i dont know about cmd shell
heres the link for 'android flasher' http://forum.xda-developers.com/showthread.php?t=794638
thanks again dude sorry if im a pain in the a...
Click to expand...
Click to collapse
But, I would say that it's a great deal easier than you're thinking, I'm assuming that you're running on a PC in which case download the IMG file mentioned above and copy it to the C:\temp directory. I've never used that tool that you suggest so can't comment on it's use.
Put your device into FASTBOOT USB (following instructions detailed above)
Then select Start->Run with mouse and type in cmd (then hit <RETURN>)
or
select with mouse Start->All Programs->Accessories->Command Prompt and click
Either of these methods should open a command shell (CMD) window on screen
Enter the following commands each followed by <RETURN> into this window:
Code:
> cd c:\temp\
> fastboot flash recovery cwm-4.0.1.4-saga.img
> adb reboot recovery
does it have to go in c:\temp? cos i cant find it lol
can i just do it from C:\Users\jammy\Downloads where it is now?
thanks
jammy2015 said:
does it have to go in c:\temp? cos i cant find it lol
can i just do it from C:\Users\jammy\Downloads where it is now?
thanks
Click to expand...
Click to collapse
in the downloads folder at the end it dont say img does that matter? it just says cwm-4.0.1.4-saga
jammy2015 said:
in the downloads folder at the end it dont say img does that matter? it just says cwm-4.0.1.4-saga
Click to expand...
Click to collapse
It doesn't matter where it goes, so long as you set the directory from within the CMD session to that place so that the commands you run find it:
So run cd C:\Users\jammy\Downloads this instead of the cd c:\temp
The file is probably still called IMG it's just that your PC isn't showing the extensions (as that's how its configured). I just downloaded it myself on my PC and it's called file.img
So still type the commands as if its called file.img though
did that an i got this message:
jammy2015 said:
did that an i got this message:
Click to expand...
Click to collapse
You need to install the fastboot EXE.
You must click on the link in my signature adb&fastboot download and then extract the downloaded ZIP file's contents to the same directory where the IMG file is currently and then re-try the command!
I believe that it should then work!
cool! so open adb folder and put it all inside the cwm-4.0.1.4-saga zip folder and then try again
jammy2015 said:
cool! so open adb folder and put it all inside the cwm-4.0.1.4-saga zip folder and then try again
Click to expand...
Click to collapse
Open the ADB folder and copy the contents to the C:\Users\jammy\Downloads
directory where that previous IMG file should be.
Afraid that I'm off out now, will check on my mobile in a little bit to see how you're doing.
good luck!
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
[Solved] Thank you all for helping me through, I finally, I can made it. See the last post of the actually summary of my own journey.
Without all of your value input, I will never made it.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
At the first place, why and how did you flash an HTC HD rom to Desire S without even knowing it?! You should have know from the start that you should have taken precautions, and known that its an HTC HD. It should be PORTED first.
To answer,
Try flashing the recovery again on fastboot. Check my guides on how to on my sig (preferrably the second one). Then see if it works. If it did, flash the CORRECT rom.
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
imkr said:
I am a bit new with this sir, sorry need a bit detail explanation.
The point is I cannot get on the recovery mode, so when I read this guide (http://forum.xda-developers.com/showthread.php?t=1314629) I feel not clear enough
Can you give me a bit more clear process, sir?
Click to expand...
Click to collapse
What I'm trying to say is to flash the recovery again. 4ext recovery recommended. And start from there. Clear instructions were given on that thread on how to flash a recovery image via fastboot, and I believe I can't simplify it much further.
imkr said:
Hi all,
I accidentally flashed a wrong ROM of HTC HD, so I'm trying to go back to recovery mode to flash another ROM of my Desire S, when I select the recovery then I am stuck on htc screen
Can someone advice me please?
Thanks.
Click to expand...
Click to collapse
Mate don't worry, it happened to me many times.see this thread to know how I got a solution.forum.xda-developers.com/showthread.php?t=1281688
I used nandroid backup but you can flash another ROM
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
After you get the phone in FASTBOOT mode, open the cmd window and type:
FASTBOOT FLASH RECOVERY c:\recovery.img
I find it very worrying that some one who can claim to have made this mistake many times is prepared to offer advice!
nandroid backups, you now see the importance of taking them
Swyped from my Desire S using XDA Premium
imkr said:
Thanks for helping me to walk through, Skanob!
I've try as the instruction:
1. Get the 4EXTRecovery_v2.1.0_saga.zip (from your signature)
2. Copy the file 'recovery.img' to C:\recovery.img
3. Connect my phone on fastboot
4. Open the cmd to type 'C:\recovery.img
5. Appear the dialog-box DVD burning 'The burn fail invalid...'
I try to do these again and again 10 times +
What should I do now?
Click to expand...
Click to collapse
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Rapier said:
The message you got is because you try to "run" in an windows command prompt an ".img" (image files). If you do so, windows try to launch the associated program with .img files. Obiviously this is the DVD burning software you have on your PC (the default windows one I think). That's why you get the error.
Now, you should pay attention very carefully to the instructions in that thread. You should NOT type "C:\recovery.img" but "fastboot flash recovery C:\recovery.img". That means you should already have installed "fastboot" application on your PC (or else you'll get a message say somthing like "'fastboot' is not recognized as an internal or external command, operable program or batch file." "fastboot" command is part of the Android SDK and should reside on your PC in the same place as "adb", that is in the "tools" (or "platform-tools" depending on what version of SDK you got) folder.
Simply, you first have to find where on your PC is installed the Android SDK. Browse with Explorer on your PC to there and look in the folders till you find the one in which "adb" and "fastboot" are. Keep the SHIFT key pressed and RIGHT click on that folder. From the menu that pops up, select "Open comand prompt here..."
Only now you can run the "fastboot" command...and if you have copied Recovery.img on the root of your C drive perform the command as instructed (an as I've wrote above). If Recovery.img is somwhere else on your pc than use it like this (after you perform steps 1-3 you've said):
fastboot flash recovery <folder_in_which_recovery.img_is stored>\recovery.img
Replace what I've wrote in italics above with the actual path to your recovery.img file.
After running this command, type the following one:
fastboot reboot-bootloader
You'll end up in 4EXT recovery from where you can flash the ROM of your will (hopefully one for Desire S this time)
Click to expand...
Click to collapse
It's working for me now, thanks for your clear instructions:
I've type up the exact process that I experienced here
1. Get 4EXT
2. Extract to C:
3. Find android-win-tools
4. SHIFT + Right click to open cmd from here
5. Type 'fastboot flash recovery C:\recovery.img', then appeared:
sending 'recovery'... OKAY (keep looking around 10mn), another command appeared
writing 'recovery'...OKAY
6. fastboot reboot-bootloader
DONE!
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.
buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?
4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work
4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.
Hey Guys! Im a newbie so cut me some slack. I attempted to root my phone using Nexus Root Toolkit. I successfully unlocked the bootloader
But the root process would fail like sometimess when it restarts my nexus s then says its booting up but it wont ! So i take the usb out let it boot then when i try to continue it finishes but its not rooted. I get the Unlocked Bootloader thing at the bottom. Help?!!?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Device:Nexus S GT-I9020a
JellyBean 4.1.2
BootLoader State:Unlocked
Rooted:No not successfully
Download superuser to usb, flash with Clockworkmod Recovery.
Stable Superuser ver 3.2 for Nexus S.
Check other superuser versions here
Follow this guide If you do not have Clockworkmod Recovery or want to learn step-by-step method; or simply download recovery-clockwork-5.0.2.0-crespo, unzip and flash with fastboot.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
P/S: Install Android SDK Tools if you do not already have fastboot. Add Android SDK Platform Tools package via SDK Manager, and fastboot.exe is found in the following directory.
Code:
C:\Program Files\Android\android-sdk\platform-tools\
_android_ said:
Download superuser to usb, flash with Clockworkmod Recovery.
Stable Superuser ver 3.2 for Nexus S.
Check other superuser versions here
Follow this guide If you do not have Clockworkmod Recovery or want to learn step-by-step method; or simply download recovery-clockwork-5.0.2.0-crespo, unzip and flash with fastboot.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
P/S: Install Android SDK Tools if you do not already have fastboot. Add Android SDK Platform Tools package via SDK Manager, and fastboot.exe is found in the following directory.
Code:
C:\Program Files\Android\android-sdk\platform-tools\
Click to expand...
Click to collapse
I tried to follow but the Img was down from MediaFire and My carrier is AT&T But im using a Telus sim
I had the same problem. I booted up and tried root dim and said I'm boot rooted.
I downloaded super-user from play store tried again and worked.
Hope this helps
Sent from my Nexus S using xda app-developers app
The link that I provided is the official recovery clockwork download link.
Superuser zip and Clockworkmod Recovery image work on Nexus S regardless of carrier and SIM.
Flash clockworkmod recovery via fastboot.
Download superuser zip to /sdcard and flash via clockworkmod recovery.
Joebizzle said:
I tried to follow but the Img was down from MediaFire and My carrier is AT&T But im using a Telus sim
Click to expand...
Click to collapse
Ok So I Unzipped it and what folder do i flash?
Joebizzle said:
Ok So I Unzipped it and what folder do i flash?
Click to expand...
Click to collapse
And can u dumb it down a little bit because Im really bad at this stuff ? Thanks
_android_ said:
The link that I provided is the official recovery clockwork download link.
Superuser zip and Clockworkmod Recovery image work on Nexus S regardless of carrier and SIM.
Flash clockworkmod recovery via fastboot.
Download superuser zip to /sdcard and flash via clockworkmod recovery.
Click to expand...
Click to collapse
This is kinda confusing can u use teamviewer and help me so you
can see my screen?
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
_android_ said:
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
Click to expand...
Click to collapse
OK
So it says sending recovery. But its just stuck on saying that and is it supposed to take long?
If you are on stock rom, clockworkmod recovery may be replaced by stock recovery upon each boot.
You can re-flash clockworkmod recovery each time you need it, or disable the recovery restoration. Search this forum for instruction on how to make recovery stick.
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
Joebizzle said:
I tried the whole Command prompt thing but it says tgings ling fastboot is not a command so thats whats getting me stuck.
Thats why i was asking if you use teamviewer so u can control my pc from ur pc. Because im confused in install/ flashing via fastboot
Click to expand...
Click to collapse
Have you got Android SDK-tools installed? Did you install the "Platform Tools" package via SDK manager? fastboot.exe is not installed by default. You may want to install USB driver too. See attached picture.
Test if fastboot is available and working: plug nexus s to pc:
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot devices
If usb driver is working, you should see some device id being displayed.
Joebizzle said:
OK
So it says sending recovery. But its just stuck on saying that and is it supposed to take long?
Click to expand...
Click to collapse
Bump.
Joebizzle said:
Bump.
Click to expand...
Click to collapse
Please see previous post #11 to test if fastboot/usb driver is working. Nexus S must be in FASTBOOT MODE.
Install Google USB driver package from SDK manager if necessary.
_android_ said:
If you are on stock rom, clockworkmod recovery may be replaced by stock recovery upon each boot.
You can re-flash clockworkmod recovery each time you need it, or disable the recovery restoration. Search this forum for instruction on how to make recovery stick.
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
Have you got Android SDK-tools installed? Did you install the "Platform Tools" package via SDK manager? fastboot.exe is not installed by default. You may want to install USB driver too. See attached picture.
Test if fastboot is available and working: plug nexus s to pc:
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot devices
If usb driver is working, you should see some device id being displayed.
Click to expand...
Click to collapse
Im just stuck on sending recovery
Joebizzle said:
Im just stuck on sending recovery
Click to expand...
Click to collapse
see post #13
_android_ said:
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
Click to expand...
Click to collapse
It says file not found?
Joebizzle said:
It says file not found?
Click to expand...
Click to collapse
Please be more specific.
To run fastboot and adb from any windows directory, you can copy the following from C:\Program Files\Android\android-sdk\platform-tools to c:\windows\system32
Code:
fastboot.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
_android_ said:
Please be more specific.
To run fastboot and adb from any windows directory, you can copy the following from C:\Program Files\Android\android-sdk\platform-tools to c:\windows\system32
Code:
fastboot.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Click to expand...
Click to collapse
I think i got fastboot and bootloader mixed up...lol
Joebizzle said:
I think i got fastboot and bootloader mixed up...lol
Click to expand...
Click to collapse
All done?
_android_ said:
All done?
Click to expand...
Click to collapse
still stuck D:
Why is this soooooo hard.!?!?!
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Cool, thanks!
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
admisi said:
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
Click to expand...
Click to collapse
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
admisi said:
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
Click to expand...
Click to collapse
Ok, I worked it out now. But for others, the problem was that recovery image was being replaced with the original on the command "fasboot reboot".
So instead, immediately after typing "Fastboot flash recovery recovery.img" I typed the following command "fastboot boot recovery.img".....AND only then did I get CWM which allowed me to flash su.zip from SD card.
Thanks for all help. Now that I have root, what changes/tweaks did you make using root?
Is there an optimum dpi to apply and are you overclocking?
Thanks.
Here is a script to reboot recovery mode; from your Android VSD220.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
Here is a script to reboot recovery mode; from your Android VSD220.
********* script starts here
#!/system/bin/sh
su
echo -n recovery | busybox dd of= /dev/block/emmc count=1 conv=sync; sync; reboot recovery
********* script ends here
I used Scripter Ver. 1.8 It work find. Don't forget to flash the right recovery.img and install su.zip. If you don't the script won't work.
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
n1gh7m4r3 said:
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I didn't know 1.3 was available. Is this a recent firmware? I checked a couple weeks ago.
Not sure, it's not my monitor, just looking at it for a friend. when I go to about, system update I see vsd220 system update 1.3 device system version : IMM76D.UI23ED02_VSC and same info under server version
Got it sorted out after hunting on google. it does work
problem with adb
Ok so i got the device being recognized on my XP machine. Really did not have to do much. Just pluged it in and everything worked.
On my Windows 7 machine when i plug in the device i only see the MTP installed and then see VSD220 in MY COMPUTER and can browse the files. I do not see it when i "adb devices".
1) USB debugging is on/enabled
2) Both laptops have Eclipse with latest ADB and ADT tools installed
Any suggestions as to what i can do? Anyone can copy over drivers that are working with your win7 machine?
Confirmed Working for Acer DA220HQL (atleast for me)
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Use at your own Risk - Acer DA220HQL
1. Download both files from the first Post (Thanks to sk8tingusmc).
Make sure they are complete and the file sizes match.2. Save "recovery.img" to your computer, and copy su.zip to the Acer DA220HQL to "/mnt/external_sd/su.zip"
3. Press Windows Key + R to open the Command Prompt or Start > Run > cmd > Enter
4. At the Command Prompt change to the Directory with adb.exe in my case "C:\Temp\sdk\platform-tools"
Download SDK from here: http://developer.android.com/sdk/index.html#download and extract in my case to C:\Temp (C:\Temp\sdk, C:\Temp\eclipse, and C:\Temp\SDK Manager.exe)5. At the Command Prompt type "adb reboot bootloader" and hit enter.
The screen will turn solid black6. At the Command Prompt Type "Fastboot flash recovery recovery.img" and hit enter.
Make sure you are in the same directory as your recovery.img.
The recovery will flash quickly
C:\Temp\sdk\platform-tools>Fastboot flash recovery recovery.img
sending 'recovery' (5688 KB)...
OKAY [ 0.176s]
writing 'recovery'...
OKAY [ 0.983s]
finished. total time: 1.163s
7. At the Command Prompt Type "fastboot boot recovery.img" and hit enter.
C:\Temp\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.173s]
booting...
OKAY [ 0.001s]
finished. total time: 0.178s
Your device will boot up8. At the Command Prompt Type "adb reboot recovery"
It will enter ClockworkMod Recovery v6.0.2.8 with Touch Support. 9. Choose ZIP File from SDCard navigate to su.zip and select it by pressing on it.
Scroll all the way down to find ++++Go Back++++ on the SDCard if you entered the wrong Directory.
You may also choose to create a Nandroid Backup if you care to do so.10. Go Back and select Reboot
11. ROM may Flash stock recovery on boot. Fix? - Yes - Disable recovery Flash
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
12. View attachment 2062751
Rom Version and work in Linux?
swiss420 said:
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Click to expand...
Click to collapse
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
LoveMyAndroid2010 said:
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
Click to expand...
Click to collapse
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
swiss420 said:
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
Click to expand...
Click to collapse
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE
Thanks for the help!
LoveMyAndroid2010 said:
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACEThanks for the help!
Click to expand...
Click to collapse
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
swiss420 said:
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
Click to expand...
Click to collapse
I did try to mount the sdcard, but I got an error that said it could not mount the sdcard. That is when I tried the sideload method. When I boot up normally, the sdcard is there along with su.zip. I posted the info on my DA220HQL noting the kernel version. I went back to the post where you stated your kernel version. They are different. Mine is later than yours.
After going through everything several times, I though maybe I was doing something wrong. We went out of town so this is the first time I could sit down and check out the posts.
Thanks for your help in advance.
Thanks for all the help. I could not get this to root so we are sending it back to HSN. As a last ditch effort, I did a factory reset and tried again. And I got the same result. I do not think that the recovery while booted was able to "see" the device's partition at all, which is why I got the mount errors. In any case, I also have found that we can find it online for much less than what HSN charged us for it. I am still curious if anyone else was able to root this little gem.
Keep posting updates!
im getting the same issue
cwm is not mounting my sdcard
android is recognizing it, but not in recovery
I'm thinking I shouldn't have installed that update
there are a bunch of errors in recovery when starting
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
my best guess is we need a different recovery img, even though acer is the same as viewsonic
also there is no prompt to disable stock recovery being reinstalled
recovery touch is also kind of wack, have to tap below whatever I want to pick (which is also not consistent horizontally)
edit: going back to recovery, under mounts and storage, it doesn't appear to have permission to mount anything
looks like viewsonic released a rooted ROM on their support site
http://www.viewsoniceurope.com/uk/support/downloads/drivers/?prod_name=vsd220
But yeah...Acer hasnt
Perhaps this should get the ball rolling? It's funny how the US site doesn't have that
edit: wow looks like they even provided flashing tools and instructions...I just hope that this doesn't brick my unit (since its Acer not Viewsonic)...anyone else willing to give it a try?