Motivation:
Ever since I got S-OFF on my G1, I set up a custom splash image. I've wanted to change this on the MyTouch Slide (espresso) since the moment I got it. Now that we have S-OFF, here's how to do this on the espresso.
Info:
The espresso stores the splash image on a write-protected area of the nand. By default, this is a white background with the red/gray '-T---Mobile-' logo with green 'MyTouch 3G Slide' logo in the center of the screen.
Prerequisite:
Must have S-OFF! see [STATUS] S-OFF for T-Mobile myTouch 3G Slide and alpharev
Install and get familiar with the Android SDK see Android SDK | Android Developers also [HOW-TO] ADB for Dummies(How-To Learner's Guide) G1 Android Development
Windows:
Extract the ffmpeg.exe file from the bin folder in ffmpeg-r25512.7z
- or Shortcut - get the getsplash.zip from gariak
Install the adb (Android Composite ADB Interface) and fastboot (Android Bootloader Interface) drivers from the android-sdk-windows\usb_driver folder
Mac:
Might find this ffmpeg guide helpful - An easy install of the ffmpeg command line tool - Mac OS X Hints
Flash:
You can set the splash by converting an image you want to a 320x480 resolution PNG file, then use ffmpeg to convert it to raw565 format using the command line:
Code:
ffmpeg -i new_splash.png -f rawvideo -pix_fmt rgb565 new_splash.img
On your computer, you can turn this back into a PNG using ffmpeg from the command line:
Code:
ffmpeg -f rawvideo -pix_fmt rgb565 -s 320x480 -i new_splash.img -f image2 new_splash.png
Then with an unlocked (S-OFF) bootloader, flash the new_splash.img file to your phone:
Code:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
References:
[Mod][HOWTO] Splash Image
gariak
[TOOL] [Linux / OSX] Splash Screen creator / flasher
gravis86
An easy install of the ffmpeg command line tool - Mac OS X Hints
Custom Boot Images here
This thread right here is way easier http://forum.xda-developers.com/showthread.php?t=543095
But you'll have to use step 3 to flash splash number 1 since we don't have special spl (danger)
I still haven't tried this but it should work flawlessy as long as you follow directions.
Note: You can get the stock splash1 screen for the mytouch slide out of the ESPRIMG.zip
AndroidFiend said:
This thread right here is way easier http://forum.xda-developers.com/showthread.php?t=543095
But you'll have to use step 3 to flash splash number 1 since we don't have special spl (danger)
I still haven't tried this but it should work flawlessy as long as you follow directions.
Click to expand...
Click to collapse
His method works fine. All it is is one code to convert the image to raw format.
Then you just gotta do the commands to get the image in there.
Here's mine. Stole it from the EVO forums.
Tested and Confirmed working, Thanks tc
arayray said:
Note: You can get the stock splash1 screen for the mytouch slide out of the ESPRIMG.zip
Click to expand...
Click to collapse
Thanks, I added it to the top post.
AndroidFiend said:
This thread right here is way easier http://forum.xda-developers.com/showthread.php?t=543095
But you'll have to use step 3 to flash splash number 1 since we don't have special spl (danger)
I still haven't tried this but it should work flawlessy as long as you follow directions.
Click to expand...
Click to collapse
Those utilities can only be used on windows. The directions above are not platform specific.
Also in those instructions, option 2 (special) and option 3 (splash1) are identical in code, so either one should work fine.
Heres a whole thread of splash screens, be careful that their the right size...
Saw a screen I liked so I modified it to work on our phones, including the bootanimation ^_^.
Eh im guessing this will only work for windows. Im on ubuntu :/ oh well ill just stick with the alpharev boot image until i get my windows back. this should be made into a sticky because i as well have been wanting to do this since i got my slide. Now that i can i dont wanna forget about this
The original instructions are not platform specific. This should work on Linux, Mac, and Windows. Ubuntu should already have an ffmpeg package... Installing the android sdk will be a little bit more than 'aptitude install ffmpeg' though...
I use a tool called BSF3k to convert to 565, ive used it on my G1 a long time ago. It's a fairly simple app.
View attachment BSF3000.zip
Edit:seems it was posted....
@OP
Dont you need to have the image in rg565?You say .img in your instructions though...
http://www.mediafire.com/?aq0tezr5ejke8uo
Nexus One Splash screen. Just converted and flashed this on my mytouch slide.
I'm trying to do this, but it keeps failing:
flash_image splash1 /sdcard/debianarchy.img
can't find splash1 partition
I have S-OFF, and the image is located on /sdcard... what am I missing here?
Don't put it on your sdcard, it has to be on your computer somewhere. Pretty sure fastboot doesn't mount your sdcard.
seems like the best way to do this is via fastboot:
0. fastboot flash splash1 debianarchy.img
1. reboot phone while holding volume down to get into fastboot
As far as I know it isn't the best way, it's the only way. Flash_image flashes data img files, not raw picture files, at least I think. I could be wrong and if a dev would like to correct me go right ahead.
the only way to flash IS through fastboot
Thanks for confirmation, that's what I thought but it doesn't hurt to have other people confirm.
just threw these together and thought i'd share. i cant take full credit bc i really only added a few things here & there.
Related
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Katzenmuetze said:
Hey guys,
beforehand: I'm totally new to this topic, so please be patient.
I got my HTC Flyer Wifi & 3G [P510e] back from reparation and the guys there also updated my Flyer to Honeycomb (3.2.1). Since I cannot use my touch buttons anymore, I would like to do a downgrade to Gingerbread again.
I've searched here and found this topics:
http://forum.xda-developers.com/showthread.php?t=1428104
http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3
Now I'm not sure what to do: do I need to S-OFF my Flyer to make a downgrade, like shown in the following thread?
http://forum.xda-developers.com/showthread.php?t=1358758
Which Gingerbread-Version do I have to use, how can I find that out? And where do I get it from?
And the most important thing: what is the worst thing that could happen if I mess up something?
My Flyer is currently S-ON, my HBOOT-Version is HBOOT-1.11.0011 (see attached file) and it's a german version, if that is important to know.
I would appreciate it if someone would help me with this. Normally I'd ask my ex-boyfriend to do this for me, but since we broke up, I want to manage this kind of stuff on my own. :fingers-crossed:
Click to expand...
Click to collapse
if you are not s-off now,then your 2nd and third links are not really of any use.
depending on wether you want to use htcdev for root,or a temporary root exploint you need to use either this thread:
http://forum.xda-developers.com/showthread.php?t=1307759 (for htcdev)
or your first link:
http://forum.xda-developers.com/showthread.php?t=1428104
the disadvantage to htcdev for root,is that it will leave a watermark that shows you have unlocked the bootloader,and as the unlock website states,this could void "all or parts of your warranty"
the disadvantage of the other link,is that the root exploit(taco root) is kind of a funky exploit,and while safe, is a little tricky to use if youre not used to doing things like this.
after you have downgraded to gingerbread,you can use revolutionary to s-off( http://revolutionary.io/ ) this leaves the door open to upgrade to honeycomb with s-off later,if you desire. it will also let you install a custom recovery,and add root access so that you can modify the stock gingerbread rom,or flash a custom GB rom, so that you can continue to operate on GB without pesky OTA notifications.
last and not least,if you cannot find a GB ruu that supports your CID (carrier identification) you will need a goldcard to downgrade to a different carrier or unbranded RUU. (directions to make a gold card: http://www.addictivetips.com/mobile...-gold-card-for-htc-desire-without-hex-editing)
just holler if you have further questions.
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
scotty1223 said:
if you decide to go the htcdev route,i have a guide with some download links that may simplify that process somewhat for you,and can reproduce it here if you desire.
Click to expand...
Click to collapse
That would be great, thank you.
TSGM said:
That would be great, thank you.
Click to expand...
Click to collapse
sorry for the delayed reply.
here is my "htcdev" guide:
i sometimes refer folks to my rezound guide in other forums,so i decided to make a slightly more "universal" version that i could replicate in other forums,so everyone has a dedicated guide,and there are not accidents with accidental application of rezound specific details or files. devices i am familiar with i will try and tweak and add device specific recovery downloads/info. whatever device youre working on,please feel free to post in this thread,i will be happy to assist you
before we get started,however,be aware that htcdev does have its limitations. it can be used if you only wish to add root access to delete bloat and run a few root requiring apps,but IMO it is best used as a "steppig stone" to get root for downgrade,or for other exploits to run. if s-off is availble on any "downgradeable to" firmware,i do highly recomend to try and achieve that goal if you wish to activly flash roms. im happy to help with this,as well,if needed.
the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files
before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-the latest custom recovery image of your choice, for your device(for the flyer,use http://hyuh.net/files/flyer/downgrade/recovery.img md5 bb366b025dcc454ffe8b21b8bf0c72d0)
-superuser files: for froyo use superuser 3.07 (found on revolutionary public wiki). for GB,HC or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.96.zip )
-go to HTCdev - Unlock Bootloader and register an account
1)unlock with htcdev
first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary
most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier
1)prepair ADB
-unzip your mini-adb.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "mini-adb_devicename" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your mini-adb_vigor directory. type the following at the prompt in your cmd window:
cd c:\mini-adb_vigor
your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)
-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your hboot to the htcdev unlock compatible version.
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:
adb reboot bootloader
it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:
fastboot devices
again,this should return your phones serial number.
-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :
fastboot oem get_identifier_token
-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens copy from below,or from htc dev:
fastboot flash unlocktoken Unlock_code.bin
-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal
as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.069s]
finished. total time: 0.070s
c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
sending 'unlocktoken' (0 KB)... OKAY [ 0.143s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.156s
c:mini-adb_vigor>
2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.
once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:
1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-temporarily launch your recovery to phone memory:
fastboot boot <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.
in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
downloading 'boot.img'... OKAY [ 1.518s]
booting... OKAY [ 0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your mini-adb directory:
cd c:\mini-adb_vigor
-make sure youre connected by typing:
adb devices
-should return serial number
-check the md5 of your recovery image:
md5sums <recoveryname>.img
**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)
-boot to bootloader:
adb reboot bootloader
-check for connectivity:
fastboot devices
-should return serial number
-permanently flash your recovery to phones recovery partition:
fastboot flash recovery <recoveryname>.img
-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.
*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.
and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]
c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.img[/COLOR]
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img 915d5e3cb662076f36f3d6e54759e951
c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
sending 'recovery' (7074 KB)... OKAY [ 1.659s]
writing 'recovery'... OKAY [ 5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot
*congratulations,youre rooted
if your device has procedures to s-off,or procedures to downgrade to more exploitable firmware,you can procede with that now
for the flyer we can use these directions: http://forum.xda-developers.com/showthread.php?t=1307759
after we downgrade to gingerbread,we can root with revolutionary:
http://forum.xda-developers.com/showthread.php?t=1194709
after yoou have s-off on gingerbread,you can update back to honeycomb:
http://forum.xda-developers.com/showthread.php?t=1358758&highlight=honeycomb+easy+s-off
if youre considering leaving htcdev unlock,read this if you want to flash roms: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html
s-off is better,and worth whatever extra efforts to achieve if available.
*hope it helps,holler if you have questions
donate to my device fund
Click to expand...
Click to collapse
gave you some links at the end to downgrade,then s-off,then upgrade back to honeycome,as well as a link that may be of some value if youre considering just unlocking via htcdev and leaving it at that. htcdev is a PITA if your intent is to flash different roms,and its even more dificult as there is no other option to chagne roms other than manually installing the boot image(i have verified that fastboot booting the recovery on the flyer does NOT provide the same advantages it does on the rezound,and other htc phones.
i will be happy to help you with any questions you have about htcdev vs s-off,or with the unlock procedure. if you just want to be rooted on the stock HC rom,htcdev unlock works,but thats about it
we can also help you with the downgrade etc. after yovue completed this,but will save that for later so we dont overwhelm you with info
Hi I need some serious help here. I upgraded my evo view that i bought used to Honeycomb. Thinking it would be better. Found out that it absolutely sucks! I am trying to roll back to GB. I already unlocked it by using the HTC DEV Unlock tool successfully. Instructions in this thread http://forum.xda-developers.com/showthread.php?t=1414137 says to flash a img. But it does not give me instructions on how to flash? Im pretty new and Ive scoured the web and have found instructions on flashing other htc phones but havent had any luck in finding one for the view. Can someone help? Please Thanks!!
ARR22 said:
Hi I need some serious help here. I upgraded my evo view that i bought used to Honeycomb. Thinking it would be better. Found out that it absolutely sucks! I am trying to roll back to GB. I already unlocked it by using the HTC DEV Unlock tool successfully. Instructions in this thread http://forum.xda-developers.com/showthread.php?t=1414137 says to flash a img. But it does not give me instructions on how to flash? Im pretty new and Ive scoured the web and have found instructions on flashing other htc phones but havent had any luck in finding one for the view. Can someone help? Please Thanks!!
Click to expand...
Click to collapse
anyone????
You're trying to do step 4, flashing recovery thru fastboot, right?
Haven't used fastboot in a while, and not at my home computer (where I have it setup for fastboot already). But from what I can remember:
1) You need the fastboot tool/drivers. The one here should work (under "Required downloads"): http://forum.xda-developers.com/showthread.php?t=1428104
I can't look at that download right now (my work internet is blocking that download site). But if its a zip, you need to unzip the contents.
2) Place the fastboot files in their own folder someplace. I usually just make a new folder in the C:\ drive parent directory for easy navigating in the next step.
3) Place the recovery image you want to flash in the same folder as the fastboot files.
4) Connect your View to the PC using USB. Reboot the View into bootloader. Select "fastboot" in the bootloader screen.
5) Open command prompt (On Windows: Start>All Programs>Accessories>Command Prompt). Change directory to the folder where you put the fastboot files.
6) Type the command into the command prompt as given in the guide you linked: fastboot flash recovery cwm-4.0.1.4-express-HC.img
I found this kind of old thread in the HTC Desire forum when I was trying to help someone with a bricked phone, and tried out this tool and thought it was kind of cool. I guess it's technically an app, but it runs on a PC (Windows or Linux) in the directory where you keep ADB and fastboot, and is a pretty slick interface to most of the fastboot commands.
To take full advantage of this you will need either an unlocked stock bootloader, or if you are S-OFF a custom bootloader like ENG, JBear or Revolutionary is preferred. A locked, stock bootloader will run only a small subset of the fastboot commands.
To install the utility just download the v1.51 file and unzip its contents to your ADB directory. Then open a command prompt in that directory and type "winrun" for windows or "linuxrun" for linux. A screenshot of the startup screen is attached.
Since this utility is just a front-end for the fastboot commands, it should work with on any Android device. Extreme caution is recommended when using this program since some ot the fastboot commands it issues can do some pretty nasty things to your phone. If you are not already familiar with fastboot commands it's probably not for you.
ramjet73
Good lookin out pimpin. Definitely gonna need this one day.
Hope I will never need it but good to have
Sent from my PG86100 using Tapatalk 2
Thanks Ramjet. Its good to have a GUI.
First, Thanks to everyone that helped me along the way here... The thanks list is in Post #2
Second, The risk obviously here is your own. This tool is provided AS IS, and I am not providing any warranty or guarantee. So it doesn't cover hail damage to your home, Tornado's taking your dog away, or your phone not working properly after using it... (or anything else that you might try to pin on me )
For all of the processes, linux is required... use your own flavor of linux and use the following to set it up:
Extract the files to somewhere (home folder works best)
Gain a root command prompt (# instead of $) (sudo -s works for most)
Set permissions via "chmod 755 ultimate" (possibly 0755 depending on linux flavor)
Then run the tool using ./ultimate
Code:
/=================================================================\
|*******************************************************************|
|****************** EVO 3D Ultimate Recovery Tool ******************|
|*************************** Version 3.1 ***************************|
|*******************************************************************|
| |
| Please Select an Option |
| |
| 1. Create a backup partition from a bricked device |
| 2. Flash a custom partition to a bricked device |
| 3. Downgrade HBOOT |
| 4. Unbrick |
| 5. VM Radio Fix (CDMA ONLY!) |
| 6. Fix radio partition (Manual Radio Fix only) (CDMA ONLY!) |
| 7. Exit |
| |
| |
|*******************************************************************|
|**************** Copyright (C) 2013, Unknownforce *****************|
|*******************************************************************|
\=================================================================/
Latest version is Here.
(3/14/13) - URTLiveCD 1.0 is available Here -> http://d-h.st/blY (This includes URT 3.0)
Recent Updates:
3.1
Added another check to the misc partition detection
3.0
Fixed and re-implemented VM Radio Fix
3.0 ALPHA
Completely Redesigned and Re-Written
New menu interface
Removed the need for hboot/misc image files to be present, they are now embedded in the program and used as necessary
CID issue fixed for GSM devices
Misc detection implemented
GSM/CDMA detection implemented
Removed Radio Fix for now, some bug I can't figure out yet... Meh
Fixed a few missing things from the VM Radio Fix (CDMA Only) (when 3.0 is Final)
Many minor bug fixes
2.5.1
Mistakenly used an older source of URT when coding 2.5, so I re-applied changes from 2.5 to the correct source and re-compiled. (No Difference for GSM, only radio fix was affected.)
2.5
Added support for GSM EVO 3D's! (add -g or --gsm)
No longer beta or RC or alpha or whatever!
Minor cleanup/optimization.
2.3 RC1
Fixed the ghost MEID issues. (This will not fix devices that got it from the first test, please contact me and I'll work with you to fix that)
Fixed some delays and timing in switching between fastboot and adb
Corrected some wording.
2.2 RC4
Second attempt at fixing output errors... Sorry :/
2.2 RC3
Attempt to fix "sh: 1: Syntax error: Bad fd number" error.
Add -f switch to attempt to fix I/O errors on possibly bad sectored emmc's (This will require being in a temp bricked state before using, if this successfully recovers them, I can add this into the process of the radio fix, for now I want to see if it's going to work at all, so it's a manual process for now, to brick device, Be S-OFF, flash custom hboot(anything but stock) and do fastboot oem writesecureflag 3, done) This is ONLY for those having I/O errors when trying to flash radio config. The usage is ./ultimate -f 19 (19 is partition 19/radio_config)
2.2 RC2
Fixed device detection at first step
Logging to log.txt
Fixed device "wait" after rebooting to system, it will now check properly that there is a device to reboot before issuing the command, rather than just rely on time.
2.2 RC1
Initial release to public
Radio Fix
Radio Fix is for CDMA ONLY!See the CDMA Thread -> here
Downgrade/Unbrick
DO NOT BRICK YOUR DEVICE IF YOU ARE S-OFF, THE DEVICE WILL NOT GO INTO EMMC MODE AS EXPECTED, AND YOU WILL HAVE A TRUE BRICK IN YOUR HANDS!!!
If you're already S-OFF, but on a higher version of hboot, you can just downgrade via a sdcard PG86IMG containing the lower hboot, being S-OFF will let it flash anything
For the S-ON Downgrade... Things you'll need...
Linux and basic linux knowledge (not necessary if you use the URTLiveCD)
The RUU ZIP image that MATCHES your current ROM version
You'll also need the 1.20 or 1.22 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
Download the ultimate3.0.zip listed above or the URTLiveCD if you do not have linux
Backup your apps/data if you need to, this process will wipe EVERYTHING
(If you're already bricked, start from Step 2)
(3/12/13 - PENDING UPDATE
I have not personally tested it, but the idea is sound and if he's done it correctly it should work just fine, If you wish to try it, it is here (Yes, it still uses Linux, but on a bootable CD) -> http://forum.xda-developers.com/showthread.php?t=1563342
First Step
VIDEO OF STEP 1 (video says Step 2, but just start here)
VIDEO OF ENTIRE PROCESS (Done with the battery pull method and on a CDMA device)
BRICK (Yes, I said brick) your device. BUT in a CERTAIN way.
You need to brick your device by corrupting the HBOOT during the HBOOT Update.
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)
1.) Take your PG86IMG ZIP image from your CURRENT ROM RUU, put it on the root of your SDCard, call it PG86IMG.zip
2.) With the phone on Battery power alone, Reboot to BootLoader, let it detect the zip and read and get to the point where it wants you to press Vol-Up to update. Do not press Update yet.
3.) Here you can do one of two things, the first being a little more easier than that second... (See Videos for examples)
3A.) The battery pull. You can interrupt the flash by pulling the battery at the right time. Tell the device to update, Pull off the battery cover (careful not to let the battery fall out) and then watch the screen and pull the battery out during or just before the orange bar shows up during the BOOTLOADER Updating.
3B.) The power pull. You can also do this by using the power cord to kill the power. Pull off the battery cover (again careful not to drop the battery out right away) then plug the device into AC power. Now pull the battery out. Tell it to update and pull the power cord at the right time.
The "right time" is different for all devices. The idea here is to completely interrupt the hboot flash so that it's corrupt. The best thing to do is to watch for the bar in the upper right hand corner, it will only show for a second (or even shorter)
If done correctly, you can plug in the device (to power or USB) and see the charge light very dim. It will need to be SOLID dim, NOT blinking dim.
The main indications that it worked correctly:
The device no longer turns on at all, no bootloader, no boot screen, nothing.
The SOLID, not blinking, dim light mentioned above.
The charge light no longer lights up when plugged in with a battery.
The device, when plugged into a windows PC, shows up as QHSUSB_DLOAD. (And MMC Storage Controller for the first 5 seconds)
The device is now bricked and ready for the next part.
Second Step
Video above shows this as well.
The next step is the linux part. Do not plug your phone in to the linux box until you are told to do so.
1.) Boot up to Linux (if you use URTLiveCD, skip to step 6)
2.) Extract your ultimate.zip file to the linux PC, Home folder is the best spot and is the easiest to work with.
3.) Open up Terminal, gain root, (su, or sudo -s)(give it your password)
4.) Run the command chmod 755 ultimate (if it's not in your home folder, add the full path to it)
5.) Type ./ultimate and press Enter.
6.) Select option for Downgrade HBOOT.
You will see the below output:
Code:
IMPORTANT: Do not plug in device until TOLD to do so.
Downgrade selected.
Ready to begin? (y/n):
Type y and press Enter.
Then you will see:
Code:
Plug in your device now.
Waiting for device...
[/CODE]
Now... plug the phone in and leave it plugged in, you should see something similar to the below:
Code:
Device Found!
Locating misc partition...
Misc found at partition 31.
Changing misc version...
Writing image file...
SUCCESS!
Flashing hboot and unbricking...
Writing image file...
SUCCESS!
All tasks Completed Successfully! Put your battery back in and boot up!
Press Enter to return to the main menu.
From there, pull your SD Card out (so it doesn't try to update from the PG86IMG.zip...) throw your battery back in, boot up to bootloader. 1.49.0007
(Some people have said that they needed to "let the device sit" for a few minutes here, mine works immediately every time, YMMV)
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.20 or 1.22 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
A few side notes:
When you run Revolutionary, you might have to do it a few times... I also didn't get to the point where it asked to flash a recovery... so I did this via fastboot, and simply used TWRP 2.0 .img file.
DISCLAIMER This is NOT a guarantee... because I'm sure it could come back... But in basic terms... I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, I have given you a method that worked for me, and SHOULD work for you, but if your house burns down, your car gets a flat tire, or your phone stops working... You are responsible for any and all of those things.
The Thanks List!
MOVZX
RussianBear
Fuses
Dexter93
TrevE
Crackanug
closeone
USSENTERNCC1701E
jcase
agrabren
chad.goodman
wwjoshdew
The Fer-Shiz-Nizzle
jlechner
The entire Revolutionary team
And pedja1 for getting me the info I needed to get the GSM port done!
FAQ's
Can I do this on Windows?
Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.
Can I do this in (Insert virtual PC software)?
The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.
Common Errors
I can't get my phone to brick, I've tried a million times!
Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.
My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it
There are several possibilities:
The phone is HTC Unlocked - You must re-lock.
The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.
I press Volume up to Update, and my phone shuts off
First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.
I'm getting Permission Denied when trying to run the linux commands
You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
Or, you didn't set the chmod correctly on the ultimate file. This is again chmod 755 ultimate (or /path/to/ultimate)
I get Misc image is missing!!! or HBOOT image is missing!!! or Recovery image is missing!!!
The hboot.img and misc.img and recovery.img files must be in the same location as the ultimate file, they are hard coded into the ultimate tool to be in the same location, their names are also hard coded, so don't rename them.
I'm getting Error 16 after running the radio fix.
This can happen, there are two things, most likely it goes away after attempting to place a few calls. If it doesn't, just remain on the line, and they can fix the problem for you.
wohohoho...great work
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that.
Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.
ramjet73
ramjet73 said:
I hope the GSM users appreciate the significance of this thread. By working together on porting this tool for the GSM model, unknownforce and pedja1 have made it possible for those of you who have gotten motherboard replacements and can't use the htcdev unlock to get S-OFF and root your phones without the need for that.
Essentially, this is an alternative to the JuopunutBear wire trick that does not require an unlocked bootloader as a prerequisite.
ramjet73
Click to expand...
Click to collapse
Oh yes, thanks to pedja1. Definitely a perfect test subject.
I'm also going to look into another method of temp-bricking the device, that doesn't require special timing or anything, more of a one-click smash and flash. But that will have to wait until I get my old EVO 3D back in a few days hopefully, when I can start testing on it.
It will be nice to be able to test without it being tied to my own number, Having a second phone is so helpful.
Here's a little preview of 3.0
Unknownforce said:
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.20 or 1.22 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
Click to expand...
Click to collapse
If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.
---------- Post added at 04:06 AM ---------- Previous post was at 04:02 AM ----------
Unknownforce said:
Here's a little preview of 3.0
Click to expand...
Click to collapse
Windows version?
zemaniel said:
If you make only RUU to 1.20, then phone start normaly, but with ICS, no IMEI and random reboot. Must do flash 1.20 like PG86IMG. Then all OK. I had this.
Click to expand...
Click to collapse
Oh, yes the first time you RUU might not fully flash everything the first time, you might have to do it a couple times.
zemaniel said:
Windows version?
Click to expand...
Click to collapse
Not possible, unfortunately.
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
A small observation.
Originally ( on ICS before downgrade) my misc partition was 32
After I downgraded to gingerbread with ruu, last partition is 31.
ICS = 32
GB = 31
Whichever last(official ruu or pg86img) you flashed tells you your misc partition
Sent from my HTC EVO 3D X515m using Tapatalk 2
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?
thanks for your hard work, this is a massive point for evo's modding :highfive:
ray650128 said:
I very want to unlock my phone, but my motherboard has replace.
So I can't unlock by HTCDev.com...
Does any GSM users can use this tool downgrade 1.53.0007 to 1.49.0007?
Click to expand...
Click to collapse
Yes, this will work for just about any version of hboot, you just need the RUU zip image from your ROM you currently are on.
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
ray650128 said:
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
Click to expand...
Click to collapse
Hmm, what was your CID before this or what is it supposed to be even?
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)
ray650128 said:
My CID is HTC__621. But now I type "fastboot getvar cid" command , it show CID is 0202.
Then I type "fastboot oem readcid" command, it show "HTC__621"
But it can't flash "1.20.401.8 PG86IMG" to my phone...(3.28.709.3 too)
Click to expand...
Click to collapse
Have you tried the RUU EXE while in fastboot USB?
ray650128 said:
Thank you very much!
I use your tool success downgrade to 1.49.0007.
But now my CID is HTC__621. I can't flash GB rom.
How can I do?
Click to expand...
Click to collapse
I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)
Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF
Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF
Then flash PG86IMG.ZIP 4EXT (using phone botloader)
Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)
All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay
zemaniel said:
I successfully performed the procedure using URT 2.5.1.
After this I flash PG86IMG.ZIP RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed
where HBoot is 1.49.0007. (using phone botloader)
Then use Revolutionary without Recovery flash - now phone REVOLUTIONARY-HBoot 1.49.0007-S-OFF
Then From PC use RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed - now phone is LOCKED-HBoot 1.53.0007-S-OFF
Then flash PG86IMG.ZIP 4EXT (using phone botloader)
Then from 4EXT flash root-OTA-ICS.zip (using phone botloader and recovery)
All OK. Phone rooted, CID_032. Original CID was also 032. No problem. Check with app CID GETTER from GPlay
Click to expand...
Click to collapse
OK, so I have a couple confirmed working... but it still doesn't sit right with me that it's not reading the CID correctly.
I'm pretty sure I know why it might have happened (the misc partition stores the CID I believe...) but I can't explain why it didn't happen for some. But I've also fixed that possibility as well in version 3.0.
Anyways, I'm leaving the link down for now, as I don't want anyone else to damage their phone this way.
I'm working on 3.0 right now, which is coming along nicely I might add. I simplified so much of the code, made it much more user friendly, and fixed a lot of the minor bugs and holes in the programming that would allow for unexpected results... Including this CID issue I believe.
Also fixed the way it writes to the log file, so it will be much easier when people can just post their log file. :good:
Once I get my device back and run through as much testing on 3.0 as I can with my own device, I'll release it for you all. :good:
I'm also looking into a better brick method, but I'm not going to release that until I actually test it... I don't know what damage it could do yet. :/
I might ask for some help from some people in the GSM world for copies of certain partitions, but more on that when I have my device back.
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job
Sent from my HTC EVO 3D X515m using XDA Premium HD app
Re: [TOOL] Ultimate Recovery Tool 2.5.1 (Unbrick, Downgrade HBOOT)
posedatull said:
No chance of getting this to work on Windows? Unfortunately my linux skills are very limited, and that combined with my lazyness to install it... I hope you get the point.
In any case, this tool seems more than awesome, great job
Sent from my HTC EVO 3D X515m using XDA Premium HD app
Click to expand...
Click to collapse
Nope windows can't detect certain things like Linux can
Sent from my SPH-L710 using xda app-developers app
As subject, i need any help and guidance for doing s-off for my rezound.
current condition : unlock bootloader, software number 4.03.605.2 710RD (unrooted and fresh stock coz i read the Pre-requisites: from the JuopunutBear's site only use stock RUU and unrooted)
since JuopunutBear / Unlimited.IO team had removed the tool for windows and only support for Ubuntu 12.04 (and newer) 32bit. # currently i use the latest ubuntu 13.04.
the instructions here http://unlimited.io/juopunutbear.htm are not too detail for newbie like me
i stuck here
"cd into the folder where you extracted and run the following cmd:
Note: This cmd returns a blank new line if you have done it correctly.
chmod 755 ControlBear adb fastboot
Run ControlBear from terminal - sudo ./ControlBear"
how to do cd into the folder in ubuntu? exactly i need more detail steps from the beginning especially from anyone who did s-off for their rezound in ubuntu, i'm very very appreciate it if u don't mind sharing with me about complete and detail from zero to success s-off rezound.
thanks so much everyone
eenpermana said:
As subject, i need any help and guidance for doing s-off for my rezound.
current condition : unlock bootloader, software number 4.03.605.2 710RD (unrooted and fresh stock coz i read the Pre-requisites: from the JuopunutBear's site only use stock RUU and unrooted)
since JuopunutBear / Unlimited.IO team had removed the tool for windows and only support for Ubuntu 12.04 (and newer) 32bit. # currently i use the latest ubuntu 13.04.
the instructions here http://unlimited.io/juopunutbear.htm are not too detail for newbie like me
i stuck here
"cd into the folder where you extracted and run the following cmd:
Note: This cmd returns a blank new line if you have done it correctly.
chmod 755 ControlBear adb fastboot
Run ControlBear from terminal - sudo ./ControlBear"
how to do cd into the folder in ubuntu? exactly i need more detail steps from the beginning especially from anyone who did s-off for their rezound in ubuntu, i'm very very appreciate it if u don't mind sharing with me about complete and detail from zero to success s-off rezound.
thanks so much everyone
Click to expand...
Click to collapse
It is assumed that people have very basic knowledge of Linux to use this...
"cd" in Linux is much like in DOS/CMD... so if you extracted your file to with the graphic interface, open a terminal and type the cd command just like you would in DOS, except use the forward slash instead of backslash... so use cd /users/eenpermana/downloads or whatever the relative folder is.
sudo ./ControlBear is a command done in the terminal to execute the ControlBear application, with superuser permissions (sudo means SUper-user DO) from the current directory.
chmod 755 on EACH of those files, not the full command as shown (it might be chainable, but I always do it individually)... so:
chmod 755 ./ControlBear
chmod 755 ./adb
chmod 755 ./fastboot
From the directory that you extracted the file. chmod changes the permissions of the files, to make them executable in this case since Linux doesn't use a files extension to determine that.
I know how to help...pm me on here and I'll help you out bud
Sent from my Rezound using xda app-developers app
Also, you could try this... https://docs.google.com/file/d/0B-tbsbTajV1UeGZ5SWhlUDU0MWM/edit?usp=sharing
It is the Windows ControlBear software for the Rezound, although not supported it does work fine for most people... But there is obviously a reason it was pulled, so YMMV and I am not responsible for any issues or problems with it or that it might cause.
Take a look HERE Using the instructions I found there, I was easily able to use the ubunto version. It is from someone else that has very little ubunto experience and turned it into a simple process.
acejavelin said:
Also, you could try this... https://docs.google.com/file/d/0B-tbsbTajV1UeGZ5SWhlUDU0MWM/edit?usp=sharing
It is the Windows ControlBear software for the Rezound, although not supported it does work fine for most people... But there is obviously a reason it was pulled, so YMMV and I am not responsible for any issues or problems with it or that it might cause.
Click to expand...
Click to collapse
mikeyk101 said:
Take a look HERE Using the instructions I found there, I was easily able to use the ubunto version. It is from someone else that has very little ubunto experience and turned it into a simple process.
Click to expand...
Click to collapse
many thanks dude
your guide and info have led me into basic ubuntu command enlighment, hhe
but new problem come to me now...exactly at the final step "wire trick" and yes the problem's here.
i think i have done all steps correctly like in the instructions and have chosen proper wire too ohh yea also about the timing.
Still unlucky for me, just stuck both on my device "blur grey htc splash screen" and on terminal "do the wire trick....." continously.
thanks again for your help at least i'm not stuck at the cd/cd/cd stuff .
may be i'll try it later while waiting for alternative ways which not using wire trick , etc and just use the similar method like htc one
btw, any suggestion about decent custom rom (global preferred but not a must) yea absolutely for the s-on and unlocked? thanks again :good:
Wire trick is pretty tricky...same if you were to use juponubears s-off...in my opinion with Verizon shutting s-off methods for their phones I think that's why it was pulled...timing and everything is a key
Sent from my Rezound using xda app-developers app
If it keeps saying to do the wire trick over and over, then it means that you are probably using the wrong type of wire and both ends are not making the proper contact. A lot of people mentioned to use an insulated paper clip but it wouldn't work for me. I ended up finding a piece of very thin stranded wire that I scavenged from an old car stereo installation harness and I got it right away. You will know that you got the proper contact when you get the success message and then have to wait for it to restart and see if you got it right. If not, you just have to run controlbear again. One trick that worked for me was to find an online metronome and set it for 48 bpm. I used this to get the timing down right. I have read of setting it anywhere from 35 beats per minute up to the 48 beats per minute that I used. The last time I did the wire trick using the Ubuntu method, I got it on the first try.
They don't call the wire trick, a trick for nothing. The one where you have to touch the contact in the hole, you have to hold the wire straight up and down to hit it.
Took me several times to get it right... keep trying, or try another piece of wire. I've used a paper clip to do it... not sure if it will shock or not so I wrapped the middle in cloth while i did it
Been using the Infection mod for quite a while I like it a lot. Have some random reboots but I think that is an issue with my phone. Super fast and pretty good on the batter, and lots of features. Also note, S-on you have to pull the boot.img and flash separately (with the adb tools, fastboot flash boot boot.img)