Related
Hello to all,
This is my first post on this forum. First of all I want to clarify to everyone that I'm spanish and I'll try to explain this in the better way I can. I've searched for similar cases but I don't know how really find a solution to this.
Today I've recivied a HTC Dream from a guy who sold it here in Spain. He said that the phone was crashed the installation of the firmware. What I've is a phone that only shows the boot image (in this case 'Telefonica Movistar', the carrier of the phone).
I can acces to the Recovery Mode by pressing 'Home + Power' and then ALT + L. In the microSD card I've a recovery.zip. It's not mine, I think that the user put on it. I don't really know because its the first Android system I touch.
When I access to the recovery mode, the first message I get is:
Code:
Android system recovery utility
E: Can't open /cache/recovery/command
I wan't to know if there is some way to go a stable version and later update to some modificated ROM with root support and extras.
Thank you in advance.
Sorry for school English.
Isern Palaus
Sorry!! This should go to 'Dream' thread.
Ask here. Read the rules before posting.
http://forum.xda-developers.com/forumdisplay.php?f=507
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
IConrad01 said:
This post is going to get moved to the Q&A section by the mods shortly, I suspect.
What you need to do is follow the instructions found on this post. They will take you through flashing the old RC9 image (in English), using the SPL rather than recovery mode. You could then, from there, flash a new recovery and ROM. (Can't help you with the language part. Don't know it -- but I'm sure it's out there.)
Click to expand...
Click to collapse
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
ipalaus said:
Hello,
First thank to you. And yes, this sould go to Q&A, so if any moderator can move, I tried editting but there is no option.
I'll try it, but I supose that you are saying RC29.
Thank another time.
Isern Palaus
Click to expand...
Click to collapse
I think he actually means RC8 for UK versions.
Hello,
I tried to flash it with the RC7 for UK versions and I got: Model ID incorrect! Update fail!
What I see on the top of the screen is:
Code:
DREAM PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
I can try with the RC29... How to know if its US or UK (EU)?
EDIT: The same with RC29.
Thanks in advance,
Isern Palaus
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Wrong thread
IConrad01 said:
Just noticed your HBoot version. Hopefully you have fastboot. (Press and hold the camera while booting up the phone, with it plugged into your computer via USB cable. Press "back" a few times; you should see "Fastboot USB" in red.)
From there, follow the instructions found here (starting w/ post # 53):
http://forum.xda-developers.com/showthread.php?t=493241&page=6
Has something to do with the fact that the European HTC Dream isn't the same as other Dreams.
From there you should pretty much be able to run any ROM you need. We hope.
As I am in the US and got my G1 during pre-order, I haven't had to go these routes.
Click to expand...
Click to collapse
Thank you! Now I'm in FASBOOT USB, of course.
I've found in this post a link to french site where they're explaining how to install a ROM (cupcake in this case i think): http://wiki.smartphonefrance.info/Default.aspx?Page=firmware-htcdream&AspxAutoDetectCookieSupport=1
In the post the only talk about changing the keys layout. Seems that this link could help, I'll try to understand it.
If you boot up the rooted kernel using fastboot, you //should// be able to run adb remount and then install the flash_image script from elsewhere. (Such as by pulling it out of the CyanogenMod ROM's .zip files)
Drop that script ("flash_image") into your phone's /system/bin folder, and then run (as root) "chmod 755 /system/bin/flash_image"
From there, you /should/ be able to run the "flash_image" script in order to flash a new recovery image (such as the RA-dream-v.1.2.2, or the Cyanogen Recovery 1.4) which would let you, from there, flash a new IPL ("radio") or SPL -- both of which are risky business -- or else you could just flash a new ROM by booting into recovery, as per usual.
The trick is to be able to successfully boot the rooted kernel image via fastboot.
Fact is, if you can do /that/, then you should /also/ be able to simply flash a new recovery image via fastboot (though you'd have to pull it out of the *.zip):
Code:
./fastboot flash recovery /path/to/recovery.img
Hopefully this is all making sense to you.
Now I've my phone full working.
The way to do it was enter with FLASHBOOT USB and use the SDK to boot.
Update with a update.zip (I used a Cupcake 1.5) and update the radios to the latests.
Thanks to all!
HELP!!
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
zerokenshin said:
my rogers htc dream just bricked on me last night it only goes to the htc logo and the boot loader thing (power key+camera key)
can anyone help me with this
thanks
Click to expand...
Click to collapse
What does the bootloader screen sat (power on holding camera )
If it was 1.33.2005 (ie was rooted) install a recovery via fastboot main version if the radio starts with 2, otherwise the -r if it starts with 3
If its 1.33.00?? Go to rogers website and download the january 911 ruu and install it.. if you want root follow the new rogers rooting directions
the bootloader screen says:
DREAM PVT 32B SHIP S-ONd
HBOOT-1.33.0009 (DREA21000)
CPLD-4
RADIO-3.22.20.17
May 12 2009,17:05:58
HBOOT
<SEND>FastBoot Mode
the phone was never rooted it just went out on me after i installed some new apps from the market place
well rooted or not with the perfected spl there is not much choice install the ruu or nbh of the official Rogers 911 rom and follow the new rerooting instructions.
If you follow all of it you will have an engineering split and can get out of this easily if it happens again.
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
zerokenshin said:
the rogers site has the HTC Dream ROM Update Utility (RUU) January 2010 is that the right thing cause if so its not working for me
Click to expand...
Click to collapse
I can't say I've ever made the RUUs work short of extracting the NBH file from your users temp directory and flashing it manually... but I always assumed I just was lazy on making the phone connect to VMWare on a mac.
Try this:
0) install fastboot/adb if you don't already have them (again I'm on a mac search for it if you need help)
1) Download http://www.rogers.com/dream-zip
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
3) enter fastboot mode on the phone
4) run 'fastboot oem rebootRUU' to put the phone into ruu usb mode
5) run 'fastboot flash nbh DREAIMG.nbh' (specifying the rogers nbh)
5b) wait for everything to flash .. this will take a few mins
6) if the phone dosn't reboot its self run 'fastboot oem powerdown' then boot normally
Once installed + running your re-rooting info is here: http://forum.xda-developers.com/showthread.php?t=733128
i dont understand step 2
2) extract DREAIMG.nbh from the zip file and put it into a directory accessible from fastboot
Hello guys,
I know the first thing you may think is this is another moron who bricked his Cell. But please be patient with me and at least let me learn from my loss. Please let me know what I did wrong.
First I read 3 main thing before doing anything,(1) [Guide] One-Click Root for Rogers HTC Dream:, (2) the post by HYKO and and finally CyanogenMod Wiki. Since I cannot post URL I attached them at the end.
So first I tried to get a hboot 1.33.2005 SPL using the source (1) which went ok.
then I used CyanogenMod Wiki (3) to root my HTC DREAM. Every thing went ok till I tried to update the radio. After I flashed the radio my cell hangs on the rogers logo and does not go any further. I can go to the fastboot (camera butt and END). it is S-off and 1.33.2005 SPL. However, I can not reach the recovery menu (Home and END). I tried flashing back to the older radio 3.22.20.17 and 2.22.29.26I (using the haykuro zip file). none of them worked.
First I want ot know what did I do wrong. Second I noticed my SDcard is broken, and the HBOOT looks for deaimg and deardiag on sd. does anyone know if I can unbrick it using this.
Thanks
alrsar
(1)
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
(3)
1. You will need fastboot on your computer to run the following commands. Set up ADB and fastboot on your computer.
2. Download exploid & Amon_Ra's Recovery:
* exploid (includes the source): Download
* Amon_Ra 1.7.0: Download
3. Rename Amon_Ra's Recovery Image to simply recovery.img.
4. Put both the exploid file & Amon_Ra's Recovery in the same directory as adb.
5. Turn on USB Debugging (Settings » Applications » Development).
6. Connect the Rogers Dream to the computer.
7. On the computer, open terminal & navigate to the adb folder
cd /path/to/adb/
8. Type in the following commands:
adb push recovery.img /data/local
adb push exploid /sqlite_stmt_journals
adb shell
cd /sqlite_stmt_journals
chmod 777 exploid
./exploid
9. You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
10. Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "secretlol".
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
NOTE: The first time this command runs, it may return "mtd: read error at 0x00000000 (Out of memory)". Simply run this command again & it should run without error.
11. The Rogers Dream has now been rooted & will have Amon_Ra's Recovery on it.
Flashing Radio
If the Rogers Dream already had the 911 patch, then the phone will already have the latest radio. Follow these instructions if the Rogers Dream did not have the 911 patch.
1. Download the latest version of the radio (3.22.26.17).
2. Rename the radio image to simply radio.img.
3. Power off the Rogers Dream.
4. Boot into bootloader mode. Hold the Camera button while powering on the Rogers Dream.
5. Connect the Rogers Dream to the computer.
6. On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
7. Type in the following command:
fastboot flash radio radio.img
8. Once finished, you can restart the Rogers Dream.
Perhaps try flashing a new recovey via fastboot?(aka screen with android skateboarding) with adb, looks at the rom bible in the dev section for more details. You also need the android sdk installed on your computer to do so, and a working mini usb cord.
ok first, you are not bricked, brick means cannot get into bootloader (camera+power) nor recovery (home+power), and it will be useless like a brick,thats why we call it "bricked" when you messed it up. Unless you use the jtag method, but thats for the super hardware geeks not for the people here in the forum.
Since you are not bricked, you can try to turn on the phone and wait for at least 5 minutes and see if the screen is still stuck on the same logo, because sometimes it takes quite long for the first boot after your new Flash. If it really stuck on the same logo for the damn 10 minutes, then you can try the following ways.
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
americanxo said:
I dont know what version SPL and radio you use, but remember, always flash the radio first, then restart the phone then flash the SPL, because this really can brick your phone (i done it once)
- if your recovery support usb mount, then re-download the roms and double check with MD5, make sure the rom is 100% identical, then reflash it. because defected rom always caused your kinda problems.
-if it still doesnt work, do this also with your SPL and Radio zip files
-if still doesnt work, get the dreaimg.nbh file to sd, then camera+power to bootloader, and downgrade to 1.0. then start to root again carefully this time.
Click to expand...
Click to collapse
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
my FASTboot command works but ADB cannot connect. I assume you mean I should flash the recovery, right?
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
From where you are flashing fastboot or rom....
If you are able to go to fastboot mode, then flash the recovery from there....using fastboot from your PC....
alrsar said:
Thanks for your reply, I have PVT 32B ENG S-OFF HBOOT -1.33.2005 drea21000
cpld-4
Radio 3.22.26.17
I can only go to the FASTBOOT mode (Camera and END) I dont have the recovery mode. So I think it rules out the first option. I can flash radio and done ut couple off time. No change to the situation. I dont know how to flash the SPL I should. Can you tell me what exactly the last option does?
thanks
Alireza
Click to expand...
Click to collapse
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
americanxo said:
the last option is to downgrade your phone to its stock version which i think it would be RC29, so you can root. I think you done it once before rooting your device right ?
Click to expand...
Click to collapse
Please please please do not flash rc29 on a rogers dream.. if the flash fails but installs the spl you can be in an annoying position, best unroot to the rogers firmware and root that again..
However op just needs to flash the -r version of the dream recovery.
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
lbcoder said:
This thread is a case of the blind leading the blind. Ignore ALL of the nonsense and read the following:
You have fastboot. That's good.
Start by installing a proper radio image. 2.22.23.02. You do this with FASTBOOT.
Go into fastboot mode, type (on your computer) "fastboot flash radio radio.img", ensuring that you have a radio.img with 2.22.23.02 in the current directory, and the fastboot executable somewhere in your path variable.
Next, flash a proper recovery image to it. Again with fastboot. "fastboot flash recovery recovery.img". Use ANY standard EBI0 recovery image that you like.
Now it'll work.
DO NOT INSTALL ANY NBH FILES!!!!!
Click to expand...
Click to collapse
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
billquinn1 said:
Since he's on Rodgers, doesn't he need the 3.22 radio and a special recovery?
Click to expand...
Click to collapse
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
ezterry said:
Shh people don't realize (ignoring carriers that may cause pain if they find a radio without an imei version of 3, only found on the latest 3.x radio) all dreams support 1.x, 2.x, and 3.x radios *if* installed properly.
The only thing to keep in mind is that like installing danger spl on a ebi0 stock dream, switching from ebi1 to ebi0 has a brick risk if done incorrectly.
To switch from 3.X->2.x or 2.X->3.x you need to flash the destination radio img file via fastboot (from hboot-1.33.2005) and *not* via recovery..
also after flashing you need to flash the recovery for the destination radio. (-r if 3.x otherwise the regular non -r)
As for if 2.x or 3.x is better.. they are nearly identical with some minor configuration changes that include some different memory offsets.. one or the other may or may not be better configured for any particular carrier.
Of corse there are many roms where we don't know what the kernel was pulled from for te ebi0 that since I don't know what kernel it has can't be used on ebi1.. I usually write these off however due to me not knowing where the source code is regardless of my target radio.
This only leaves the interesting aspect of lbcoder.. the amount he screams to ebi0 users not to use danger spl due to the dangers, but requests rogers/ebi1 users to switch to ebi0 radios despite the danger.. (note don't take this as you should or shouldn't do either recommendation, but that you need to understand what the approach means and what is your goal.. if you just want to access root to remove some bloat ware all you need is exploid or androot and you can keep the stock firmware.)
Ultimately however I expect people to take lbcoders advice with a grain of salt; and hopefully this will make the user actually read up on his suggestions, and what they where originally planning.. and figure out how to safely go from where they are to where they are going.
Click to expand...
Click to collapse
Interesting stuff. I always thought there was a (carrier + hardware) reason for the different radio. Thanks for taking the time to explain.
Hey guys,
Yesterday i was wondering about installing custom rom to my galaxy s, but i have a little problem. When i open ROM manager and choose install from sd card and find my rom there, then one step in installing process just freeze. I use clockmod recovery v.2.5.1.2 and it freeze with every rom in Installing update step. Maybe someone can help me??
At the moment i have 2.1 official software and 2.2 is not supported in my region. I have rooted my phone with oneclickroot
"[WARNING!] Do Not flash Any ROM until you can get the 3 buttons DOWNLOAD MODE workin"
I don't understand what that means?
I have GT-I9000 International and i cant get to flash menu using combination vol up+ home key + power key
My phone:
Model number GT-I9000
Firmware version: 2.1 -update1
basedband version I9000XXJM3
Kernel version 2.6.29 [email protected] #2
Build number ECLAIR.XWJM5
Please help me
sc0rpp said:
"[WARNING!] Do Not flash Any ROM until you can get the 3 buttons DOWNLOAD MODE workin"
I don't understand what that means?
I have GT-I9000 International and i cant get to flash menu using combination vol up+ home key + power key
Click to expand...
Click to collapse
I believe that there's a solution to get your three buttons working. You need those three button combination in order to flash roms via odin/heimdall or through clockworkmod recovery.
Sent from my GT-I9000 using XDA App
rafi92 said:
I believe that there's a solution to get your three buttons working. You need those three button combination in order to flash roms via odin/heimdall or through clockworkmod recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I can also go to clockworkmod recovery using rom manager, but i read http://forum.xda-developers.com/showthread.php?t=810685 this thread and there says that do not flash any roms if 3 buttons comb does not work, so basicly what shall i do?
sc0rpp said:
I can also go to clockworkmod recovery using rom manager, but i read http://forum.xda-developers.com/showthread.php?t=810685 this thread and there says that do not flash any roms if 3 buttons comb does not work, so basicly what shall i do?
Click to expand...
Click to collapse
That thread has a solution to solve the 3 button. Do that first.
Sent from my GT-I9000 using XDA App
http://forum.xda-developers.com/showthread.php?t=785201
But first i want to know ist this method working on me?
PDA: I9000XWJM5
PHONE: I9000XXJM3
CSC: I9000OXEJM1
I want just be sure that it does not broke my phone.
sc0rpp said:
http://forum.xda-developers.com/showthread.php?t=785201
But first i want to know ist this method working on me?
PDA: I9000XWJM5
PHONE: I9000XXJM3
CSC: I9000OXEJM1
I want just be sure that it does not broke my phone.
Click to expand...
Click to collapse
Yes follow the method on the link which you have given to get your 3 button recovery/download working FIRST before flashing a new ROM.
I assume you are very familiar with Odin since you know all those terms.
DO NOT flash a ROM without doing the 3-button recovery/download.
I dont understand about this: 5. Start a new command prompt and navigate to the folder / drive where adb is located.
If you haven´t downloaded adb yet, get it here.
I start a new command prompt, but what i must write there? Also i have unzip adb with 2 .dll files.
sc0rpp said:
I dont understand about this: 5. Start a new command prompt and navigate to the folder / drive where adb is located.
If you haven´t downloaded adb yet, get it here.
I start a new command prompt, but what i must write there? Also i have unzip adb with 2 .dll files.
Click to expand...
Click to collapse
Download the Android SDK from here:
http://developer.android.com/sdk/index.html
Get the .zip version.
For easy access extract it to your desktop.
After extracting run command prompt.
type in "cd desktop" followed by "cd android-sdk-windows"
From there, type in "cd tools", and then you can type in "adb reboot download"
You MUST extract it to your desktop in order for all the commands which I've put down to work.
when i type "adb reboot download" then i got error like 'adb' is not recognized as an internal or external command, operable programm or batch file.
okey i have finished the protsess and i worked Thanks!
sc0rpp said:
okey i have finished the protsess and i worked Thanks!
Click to expand...
Click to collapse
No problem. If you need any help just post it here
Cheers!
HTC HOLIDAY SUPERGUIDESTOCK ICS ROOT NOW WORKS
***(BEFORE YOU BEGIN)
- You MUST be on a stock ROM with the bootloader locked or re-locked
- If you are NOT locked/re-locked or you are on a custom ROM, then you MUST follow the following directions...
- Boot into H-Boot by powering off. Once off, power back on and hold VOL DOWN + POWER BUTTON, once in HBOOT go to "fastboot" and click the power button to select
- Download the WCXJB ROOT PACK zip from the bottom to your desktop and unzip it
- Inside the unzipped WCXJB ROOT PACK folder, hold SHIFT and RIGHT CLICK, select open a command window here
- Run this code in the command prompt without quotes
- "fastboot oem lock"
- Now reboot
- Now, we will flash you back to the original stock ROM you were on
- Pick the RUU for your specific device. For example, the one for AT&T has the word "Cingular" in it, the one for Rogers says "Rogers" in it.
- You will find the RUU's here http://www.filefactory.com/f/002b74e0f4775869/ (THANKS to user football)
- Once you download the correct RUU, make sure your phone is plugged in via USB to your computer and you have the correct drivers (or just HTC Sync) installed on your computer
- Run the executable and follow the steps to flash the stock ROM
- Once the ROM loads, you can move on to the next steps
Click to expand...
Click to collapse
***(IF YOU ARE ON AT&T AND YOU DON'T WANT TO S-OFF)
- Go here and under software downloads, download the file that is over 400mb
- Follow the instructions that are listed right above the download button to run the RUU
- Once that is done, do step 1 and then step 4. I repeat, SKIP steps 2 and 3.
Click to expand...
Click to collapse
1) Unlock the bootloader via HTCdev website
- You need to go the the HTC dev website and do the unlock (THIS WILL WIPE ALL YOUR PERSONAL DATA). You must follow the exact instructions they give you. Most people seem to have the biggest problem with the token.
http://htcdev.com/bootloader
- Tip: When copying your token, start with and INCLUDE the line that says "<<<<< Identifier Token Start >>>>>", end with and INCLUDE the line that says "<<<<< Identifier Token End >>>>>"
- Tip 2: Do NOT include the "INFO" portion of every line
- Tip 3: Keep the bin file it gives you just in case you need to relock the bootloader in the future
- Tip 3: On Linux, when getting the token, remember to run fastboot under sudo
Click to expand...
Click to collapse
2) S Off the device (Juopunutbear/WildChild)
- MAKE SURE YOU ARE ON A STOCK ROM WITH AN UNLOCKED BOOTLOADER
- Download the WCXJB ROOT PACK zip below to your desktop and UNZIP it
- On your phone, make sure in your settings, USB Debugging is ENABLED in development
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot flash recovery wcxrecovery.img"
- Now you can boot up your phone
- Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now ready to S-OFF
- Go to the link below and click the URL in the first post and follow the instructions
http://forum.xda-developers.com/showthread.php?t=1576668
Click to expand...
Click to collapse
3) Update the HBOOT (Juopunutbear)
- If you haven't already, download the WCXJB ROOT PACK zip below to your desktop and UNZIP it
- Make sure in your settings, USB Debugging is ENABLED in development
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK you just downloaded, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot erase cache"
- "fastboot oem rebootRUU"
- "fastboot flash zip jb_hboot.zip"
Click to expand...
Click to collapse
4) Perm-Root your device (WildChild)
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot flash recovery wcxrecovery.img"
- Now you can boot up your phone
- Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now rooted and I recommend flashing a matching kernel + ROM for root to stick
Click to expand...
Click to collapse
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
FIRST (AUTO) (joeykrim's FlashImageGUI method)
http://forum.xda-developers.com/showthread.php?t=1423151
OR
SECOND (AUTO) (xboarder56's method)
- First, turn off wifi on your phone
- If you have SetCPU installed or any other program where you have altered to overclock or underclock, DISABLE the "set on boot" option
- You will have to download Easy Kernel Flasher v03.zip which is attached below
- Next plug in your phone and make sure its getting detected
- After that extract the zip file (kernel flasher)
- Place the boot.img of the kernel you want flashed in the "Kernel-Here" folder.
- Make sure android debugging is enabled on your phone via settings
- Click Flash.bat for windows or Flash.sh for linux and wait for it to close terminal
- Wait for your phone to reboot and wait 5-10 minutes. Then reboot again and wait 5 minutes, then you're good to go!
http://forum.xda-developers.com/showthread.php?t=1328141
OR
THIRD (Manual) (Pirateghost's method)
- Extract the boot.img out of the kernel file or ROM zip that you want and put it in the same directory as your fastboot.exe/fastboot executable (it might be easiest to download the WCXJB_ROOT_PACK.zip from below and unzip it, put the boot.img in there)
- Boot phone into hboot/bootloader (make sure you are in fastboot mode)
- Connect phone to PC
- Inside the unzipped WCXJB_ROOT_PACK folder, click shift + right click, select "open a command window here"
- Enter these codes separately to flash the kernel and reboot the phone
Code:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
(Optional) Flash a custom ROM
*ATTENTION* IF FLASHING A KERNEL IS NEEDED FOR THE ROM YOU WANT TO FLASH, FLASH THE KERNEL FIRST, THEN THE ROM AFTER, OR ELSE YOU MAY BOOT LOOP.
1) Download a ROM, it should be in a zip file (MAKE SURE the ROM is pre rooted, or else you might lose root. If you do not know, ask the respective dev)
2) Connect your phone to your computer through the USB and mount the storage card (storage mode)
3) Copy the ROM you downloaded and put it on the ROOT of your storage card (not in any folders)
4) Power off your phone. Then power it on holding the POWER and VOLUME DOWN buttons. You should be in H-Boot, now use the volume rocker to select recovery (the power button "selects" it)
5) Once in recovery, scroll down to "backup and restore" and select it, now select "backup". This will give you a safe ROM to fall back on and restore in case anything goes wrong
- IF YOU ARE HAVING ISSUES WITH BACKING UP, pull the battery, boot back into recovery (power + vol down then select recovery) and try again. OR you may have to boot up and delete the old partial backups with a file explorer and try again. OR make sure your USB is no longer connected and try again.
6) Get back to the main recovery menu and select "wipe data/factory reset". Select "Yes" when prompted.
7) Get back to the main recovery menu and select "wipe cache partition". Select "Yes" when prompted.
8) Get back to the main recovery menu and select "advanced". Now select "Wipe dalvik cache" and select "Yes" when prompted.
9) Get back to the main recovery menu and select "Install zip from SD card". Choose the ROM you just put on the storage card, and select "Yes".
10) IF your ROM will not install correctly or you get an error and you are using the recovery from the superguide (this one) then tell the dev of the ROM to update their script to work with the new recovery
11) Get back to the main recovery menu and select "Reboot now". Your ROM will now be loaded up. Do not panic if it takes a small while (5 minutes at most I'd say) because the first boot always takes some time.
Click to expand...
Click to collapse
(Optional) Remove CIQ (8125Omnimax's method)
Go here and follow every step precisely
http://forum.xda-developers.com/showthread.php?t=1415335
Click to expand...
Click to collapse
Wondering about a basic question? Look in this General Knowledge Thread to see if your answer is there.
MORE INFO IN THE SECOND POST
THANKS to GSLEON3, EvilDevnull, WildChild, xboarder56, erik10002, frigid, 8125Omnimax, Pirateghost, thecubed, bjg222, drewdatrip, pside15 (let me know if I missed anyone else)
(If you think I am missing something, please tell me and I'll add it )
6) (Optional) Return to stock (locked bootloader, unrooted, etc) (Many thanks to Pirateghost)
- First, you are going to need to re-lock your bootloader.
- Boot into H-Boot by powering off. Once off, power back on and hold VOL DOWN + POWER BUTTON, once in HBOOT go to "fastboot" and click the power button to select
- Download the adbfastbootrecovery zip from the bottom of the post and EXTRACT it to your desktop
- Go to your computer file explorer and find your desktop "folder", hold SHIFT and RIGHT CLICK, select open a command window here
- Run this code in the command prompt
Code:
fastboot oem lock
- Now reboot
- Now, we will flash you back to the original stock ROM you were on. There are two options for this, the second does NOT need a windows device.
FIRST OPTION (RUU)
- Pick the RUU for your specific device. For example, the one for AT&T has the word "Cingular" in it, the one for Rogers says "Rogers" in it.
- You will find the RUU's here http://www.filefactory.com/f/002b74e0f4775869/ (THANKS to user football)
- Once you download the correct RUU, make sure your phone is plugged in via USB to your computer and you have the correct drivers (or just HTC Sync) installed on your computer
- Run the executable and follow the steps to flash the stock ROM
- Once the ROM loads, you should be good to go
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
OR
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
..........
radi0chik said:
can anyone confirm that HTC supertool works with the vivid?
Click to expand...
Click to collapse
Works great
Woohoo! Thanks all Finally rooted!
radi0chik said:
Woohoo! Thanks all Finally rooted!
Click to expand...
Click to collapse
Good deal
Sent from my HTC PH39100 using xda premium
Just a quick question, is there a way to relock the bootloader?
markjo said:
Just a quick question, is there a way to relock the bootloader?
Click to expand...
Click to collapse
Yes. That is why the guide says to keep that bin file. However, relocking the bootloader does not necessarily fix your voided warranty. If relocked, your device will not show up as "Locked", it will show up as "Relocked" to HTC.
You could add a part about flashing custom kernels like the one for the hollicakes ROM. That was even confusing to me and I've flashed numerous phones hundreds of times.
pside15 said:
You could add a part about flashing custom kernels like the one for the hollicakes ROM. That was even confusing to me and I've flashed numerous phones hundreds of times.
Click to expand...
Click to collapse
I was actually thinking about doing that earlier but got cut short in time. I'll add it though.
Sent from my HTC PH39100 using xda premium
Looks great, thanks for collecting all this stuff in one place! So happy to finally have a bootloader unlock, CWM, and permanent root!
bjg222 said:
Looks great, thanks for collecting all this stuff in one place! So happy to finally have a bootloader unlock, CWM, and permanent root!
Click to expand...
Click to collapse
Thanks man. It didn't take too long, maybe 20-30 minutes. The flashing ROM and kernel parts may be a little outdated though. I took them from old notepad files from when I had my Inspire. Oh well, it still should do the job .
So I followed your guide and was able to unlock my bootloader, and root my phone. It is hard to tell if it truly is rooted or not, but I loaded up a couple
apps that only work when rooted and SuperUser passed them through. Good stuff all around
However that WiFi tether just doesn't seem to be working for me. I turn it on, connect my MAC but then can't actually get on the internet.
I know when I had my Inspire, I would a custom ROM on and I was able to just turn on mobile hotspot in the settings area and it worked without saying I needed a plan. Is there anything like that for the Vivid? Or does someone need to make a custom ROM with that feature included.
I mainly need root, so I could get that feature, everything is perfect!
verseman said:
So I followed your guide and was able to unlock my bootloader, and root my phone. It is hard to tell if it truly is rooted or not, but I loaded up a couple
apps that only work when rooted and SuperUser passed them through. Good stuff all around
However that WiFi tether just doesn't seem to be working for me. I turn it on, connect my MAC but then can't actually get on the internet.
I know when I had my Inspire, I would a custom ROM on and I was able to just turn on mobile hotspot in the settings area and it worked without saying I needed a plan. Is there anything like that for the Vivid? Or does someone need to make a custom ROM with that feature included.
I mainly need root, so I could get that feature, everything is perfect!
Click to expand...
Click to collapse
To double check root, I use Root Checker (just search the market for Root Checker), and it'll tell you. Also, TitaniumBackup will tell you if you're rooted or not when you start it.
As for WiFi Tether, rooting by itself doesn't unlock that feature. Most custom roms make tweaks to enable it. So far, it doesn't look like anybody's found to right way to release the AT&T check that's performed when trying to turn it on, so in the stock ROM, you still won't be able to use if without the proper plan. There's been enough posts asking about it, though, that I'm sure a way will show up soon enough. I'm poking around in the system files right now to see if can find something useful.
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Having trouble with the HTC Super Tool. The drivers file won't launch, and when I try to run the bat file it says file path not specified... I am running windows using parallels on Mac OSX Lion. It's just weird that the driver file won't open up and run completely. I even tried running as admin.
Also, when i connect it to the computer, do i pick just charge only, htc sync, or disk drive? Or does it matter?
cyber_pete said:
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Click to expand...
Click to collapse
This has been reported working for.the Vivid once the bootloader is unlocked.
Sent from my HTC PH39100 using xda premium
cyber_pete said:
Nice job getting all this in on place.
One question:
3) (Optional) Custom CWM Recovery
Go here and follow every step precisely
http://forum.xda-developers.com/show....php?t=1343625
This thread looks like it is for creating a CWM Recovery and root do both files need to be used and is this working on Vivid as well as Raider? (I know it should just don't want to assume)
adbfastbootrecovery.zip (this seems to be the recovery file)
VIVID_CWM_ROOT.zip (this one seems to be for rooting, is this one necessary as well to ge the recovery?)
Thanks just don't want to screw up and have to reload everything since I can't do NAND yet.
Click to expand...
Click to collapse
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
bjg222 said:
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
Click to expand...
Click to collapse
the idea behind using the CWM rooting method is that you dont have to root using any kind of exploits. the exploits were leaving residual problems with sdcard mounting and the CWM is the much cleaner way of rooting. those residuals may not exist any more, but when i threw the CWM together, it was because of a request for it, and it didnt require an exploit.
slapshot30 said:
This has been reported working for.the Vivid once the bootloader is unlocked.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
In reality, it might be best to just do the steps involving flashing the recovery, as using the SuperTool, su & busybox are already installed. So I think all that's needed are steps 2 - 6, as the rest deal with stuff already done by the SuperTool
bjg222 said:
There's no need to flash the VIVD_CWM_ROOT.zip if you root using the SuperTool. I used the SuperTool (options 1, then 2 - prep, then root) to get root, then flashed CWM using the fastboot command given in the linked thread. Worked like a charm. I suppose it would work just as well, however, if you unlock the bootloader, flash CWM, then flash the VIVID_CWM_ROOT.zip, bypassing the SuperTool all together.
Click to expand...
Click to collapse
I'll update the post, thanks for that. Do you think doing away with the supertool would be an easier method then?
Sent from my HTC PH39100 using xda premium
hey all..so im a total noob at this and im so lost right now..i am trying to s off this htc holiday,,
this is where i am at so far...i have restored to factory flash from this thread,http://forum.xda-developers.com/showthread.php?t=2013122
i then did the htc dev unlock and rooted the phone using this method 2) S Off the device (Juopunutbear/WildChild)
- MAKE SURE YOU ARE ON A STOCK ROM WITH AN UNLOCKED BOOTLOADER
- Download the WCXJB ROOT PACK zip below to your desktop and UNZIP it
- On your phone, make sure in your settings, USB Debugging is ENABLED in development
- Turn off your phone, turn it back on my holding power + volume down
- Use the volume rocker and power button to select fastboot
- Connect your phone to your PC
- Inside the WCXJB ROOT PACK, click shift + right click and select "Open command window here"
- Enter in these commands without the quotes
- "fastboot flash recovery wcxrecovery.img"
- Now you can boot up your phone
- Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now ready to S-OFF
i have su and root checker comes back rooted..
but in the superguide it says i should now flash kernal and matching rom???? i wont be stock then so how can i s off???
after gaining my root the way above i ran control bear and this is what i get.first pic..second pic is my menu if it helps..
any suggestions or a good walk through maybe..thanks alot eh..been at this two days..all i wanna do is s off..
have been following the step guide here...http://forum.xda-developers.com/showthread.php?t=1416836
Did you do the 2nd part of the instructions you posted?
"Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now ready to S-OFF"
The CWM (ClockWorkMod) is a back up utility. It is what comes up when you select Recovery (right under Fastboot). I suggest you run it once you achieve your s-off. It will back up your phone onto the MicroSD card you've put in near the battery.
On another note:
I suggest you flash to Super CID once you get s-off to work. I had to try 4x or 5x to get the wire trick to take for s-off, but it did work in the end.
super CID allows you to flash any rom from any country without issue.
Here's what mine looks like:
yes i did the second part i have superuser now..and it did authenticate root checker, so its working..kinda why im stumped..
and Controlbear finds device and doesnt give root error just the one mentioned in pic..ty for reply and help btw...
Spazmogen said:
Did you do the 2nd part of the instructions you posted?
"Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
- Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
- Select "install zip from sdcard"
- Select the VIVID_CWM_ROOT_VER2.zip through recovery and then reboot your phone
- You are now ready to S-OFF"
The CWM (ClockWorkMod) is a back up utility. It is what comes up when you select Recovery (right under Fastboot). I suggest you run it once you achieve your s-off. It will back up your phone onto the MicroSD card you've put in near the battery.
On another note:
I suggest you flash to Super CID once you get s-off to work. I had to try 4x or 5x to get the wire trick to take for s-off, but it did work in the end.
super CID allows you to flash any rom from any country without issue.
Here's what mine looks like:
Click to expand...
Click to collapse
Ensure USB debugging is enabled in your settings (under Development tab).
Go into the SuperUser program (in your apps) and tap to update the binary file.
I suggest running the Control Bear process again and of course the wire trick when it tells you to.
I was rooted and had CWM installed before I tried to s-off.
Check your Recovery. It should look like this:
If your recovery does not, I suggest running the install of it again.
You sound as though you're 1/2 way to getting the s-off done. Stick with it.
I can't explain how to fix... but your problem is you're not able to grant root via ADB...
I know one solution is to use faux's kernel
Sent from my Vivid 4G using Tapatalk 2
yep thats my recovery..used it to flash the vivid cmw..
and yep debugging is on or control doesnt find device..
tindean said:
if i cmd the adb devices,,my device shows up as well when i fastboot devices my phone shows up? is this what you meant??
Click to expand...
Click to collapse
No... just because and can see it... doesn't mean you have root...
Like I said... you can most likely fix it by flashing faux's kernel...
I think 'adb remount' is the command to check for root via adb
Sent from my Vivid 4G using Tapatalk 2
i flashed with grouper-faux123-reset-kernel-4.1.2 and i still have the same error in pic above in controlbear??
anything else i can give a try?thanks
is it possible to use a rooted rom and still s off?
you flashed a nexus 7 kernel.........
ok ty..my phone still works lol..flashing back to stalk now..starting over thanks eh...
if i had have flashed with proper flash think it would have made adb root?
reflashed to stock rogers ruu..rooted with wcjxb and vivid cwm...then flashed boot.img(faux) from darkraider 155. im still getting the original error in control bear about secondary backup...whats to do??
Did you ever launch the SuperUser app and update its binary as I suggested previously? It may not help, but it sure won't hurt.
You'll know for certain if you're rooted if you can do that.
morning..yes i tried the su update..is this proper in the pic..
i can fastboot adb devices and fastboot devices. when i try adb remount it returns an error tho..im stumped...
thanks for all the help here btw..i made a mess around here a lil..
If anyone went to http://www.unlimited.io/juopunutbear.htm recently, it explains you have to do use Ubuntu 12.04 (and newer) 32bit only, and the guides here are out dated, I went from the s-off method here, to s-on, and ran Ubuntu and s-off'd again using the updated method and I have less problems than I did before.
read that but ive read windows version should work?? hmmm ill try the process on another machine running ubuntu or 7..
thanks
It should work. I've been using the original method for about a year and 0 problems.
Sent from my HTC PH39100 using Tapatalk 2
XxSHaDoWxSLaYeRxX said:
It should work. I've been using the original method for about a year and 0 problems.
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Lol. Yep Shadow, I think the same! Has to be something
Small I'm missing. Thanks again. Don't know where to go from here
Finally got it. Thanks for your replies.
Just realized I may have gotten more help with a thread title.
Thanks again